Rev 5083: (mbp) fix rst in admin guide (Alexander Belchenko) in file:///home/pqm/archives/thelove/bzr/2.2/

[Canonical.com Patch Queue Manager]

At file:///home/pqm/archives/thelove/bzr/2.2/

------------------------------------------------------------
revno: 5083 [merge]
revision-id: pqm at pqm.ubuntu.com-20100908094908-3mje9kjg540g9bql
parent: pqm at pqm.ubuntu.com-20100820035357-4p7z0fnmgcrvucuh
parent: bialix at ukr.net-20100906204757-mecxk7vn3mxgvlgd
committer: Canonical.com Patch Queue Manager <pqm at pqm.ubuntu.com>
branch nick: 2.2
timestamp: Wed 2010-09-08 10:49:08 +0100
message:
  (mbp) fix rst in admin guide (Alexander Belchenko)
modified:
  doc/en/admin-guide/simple-setups.txt simplesetups.txt-20091205144603-lgpl0e0z6lzk2rdw-11
=== modified file 'doc/en/admin-guide/simple-setups.txt'
--- a/doc/en/admin-guide/simple-setups.txt	2009-12-07 21:51:01 +0000
+++ b/doc/en/admin-guide/simple-setups.txt	2010-09-06 20:47:57 +0000
@@ -3,7 +3,7 @@
 
 Consider the following simple scenario where we will be serving Bazaar branches
 that live on a single server.  Those branches are in the subdirectories of
-``/srv/bzr`` (or ``C:\\bzr``) and they will all be related to a single project
+``/srv/bzr`` (or ``C:\bzr``) and they will all be related to a single project
 called "ProjectX".  ProjectX will have a trunk branch and at least one feature
 branch.  As we get further, we will consider other scenarios, but this will be
 a sufficiently motivating example.