#
#
# patch "wiki/TroubleShooting.mdwn"
#  from [9051942347a96559014297249e18883814ed67ce]
#    to [e26c545f452bb48e9fa076e61d2bb7d0c523f58c]
#
============================================================
--- wiki/TroubleShooting.mdwn	9051942347a96559014297249e18883814ed67ce
+++ wiki/TroubleShooting.mdwn	e26c545f452bb48e9fa076e61d2bb7d0c523f58c
@@ -95,6 +95,7 @@ and
     mtn sync myhost.com '*'
 
 and
+
     mtn sync myhost.com "*"
 
 ...will both undergo glob expansion, resulting in a command-line which contains a list of files in the current directory.  To get around this, use
@@ -110,20 +111,20 @@ A bug in monotone right now is that it d
 * checking the server log for any notes about permissions
 * make sure your read permission file is correct -- it is in a simple little language that looks like:
 
-    pattern "*"
-    allow "address@hidden"
-    allow "address@hidden"
+        pattern "*"
+        allow "address@hidden"
+        allow "address@hidden"
 
-  to allow Abe and Beth read access to all branches, or
+    to allow Abe and Beth read access to all branches, or
 
-    pattern "foo*"
-    allow "*"
+        pattern "foo*"
+        allow "*"
 
-  to allow anonymous access to all branches whose names begin "foo".
+    to allow anonymous access to all branches whose names begin "foo".
 * make sure your write permission file is correct -- it is **not** the same format as the read permission file, because write permissions are per-db, while read permissions are per-branch.  (This has to do with the somewhat amorphous nature of monotone branches.)  A write permissions file might look like
 
-    address@hidden
-    address@hidden
+        address@hidden
+        address@hidden
 
 *Add an 'x' here if this helped you*: