--- a/ContributingCode.wiki	Thu Jan 14 20:35:51 2016 +0000
+++ b/ContributingCode.wiki	Thu Jan 14 20:38:19 2016 +0000
@@ -36,14 +36,14 @@
 === Using (named) branches ===
 Branches are alternative commit histories. Changes done in one branch can be merged into other branches as needed.
 
-Most main development happens on the main repository branch "default".
+_Most main development happens on the main repository branch "default"._
 
 
-We prefer not to use separate branches for little patches, as branches are permanent and will clutter the list of {{{hg branches}}}.
+We prefer *not* to use separate branches for little patches, as branches are permanent and will clutter the list of {{{hg branches}}}.
 
-So for small code contributions, use "unnamed branches" instead (see below).
+*So for small code contributions, use "unnamed branches" instead (see below).*
 
-However, if you are going to write code that is more a project than a patch and that will take dozens of commits, feel free to do that work on a new branch.
+_However, if you are going to write code that is more a project than a patch and that will take dozens of commits, feel free to do that work on a new branch._
 
 To create a new branch use {{{hg branch}}} followed by the name of the new branch, before committing the first code.