README.md: Remove emphasis

[code/vcsh.git] / README.md

diff --git a/README.md b/README.md
index f13a959fc34e62e9fcd1e04086118c3ff0de3690..41997d54517c03244cfc9a821e4521841a849ae8 100644 (file)
--- a/README.md
+++ b/README.md
@@ -54,21 +54,21 @@ They can all be found [on the author's talk page][talks].
 ## 3.1 Comparison to Other Solutions ##
 
 Most people who decide to put their dotfiles under version control start with a
-**single repository in $HOME**, adding all their dotfiles (and possibly more)
+single repository in $HOME, adding all their dotfiles (and possibly more)
 to it. This works, of course, but can become a nuisance as soon as you try to
 manage more than one host.
 
 The next logical step is to create single-purpose repositories in, for example,
-~/.dotfiles and to create **symbolic links in $HOME**. This gives you the
+~/.dotfiles and to create symbolic links in $HOME. This gives you the
 flexibility to check out only certain repositories on different hosts. The
 downsides of this approach are the necessary manual steps of cloning and
 symlinking the individual repositories. It will probably become a nuisance when
 you try to manage more than two hosts.
 
-**vcsh** takes this second approach one step further. It expects
-**single-purpose repositories** and stores them in a hidden directory (similar
+vcsh takes this second approach one step further. It expects
+single-purpose repositories and stores them in a hidden directory (similar
 to ~/.dotfiles). However, it does not create symbolic links in $HOME; it puts
-the **actual files right into $HOME**.
+the actual files right into $HOME.
 
 Furthermore, by making use of [mr] [1], it makes it very easy to enable/disable
 and clone a large number of repositories. The use of mr is technically optional