Update folly/docs/Synchronized.md

Summary:
Fixed escaping bug where the `>` in `operator->` was
interpreted as starting a code block.  Folly github pull #15.

Test Plan: no

Reviewed By: njormrod@fb.com

FB internal diff: D582873

diff --git a/folly/docs/Synchronized.md b/folly/docs/Synchronized.md
index 5e719037c34f6ee7c27b2ea10e55c4900ec422de..a7e2768074ba45c7b4cf9c04c673fad848b976b4 100644 (file)
--- a/folly/docs/Synchronized.md
+++ b/folly/docs/Synchronized.md
@@ -265,8 +265,8 @@ iteration a la:
 is a crime punishable by long debugging nights.
 
 If the `Synchronized<T>` object involved is `const`-qualified,
 is a crime punishable by long debugging nights.
 
 If the `Synchronized<T>` object involved is `const`-qualified,

-then you'll only be able to call `const` methods through `operator-
->`. So, for example, `vec->push_back("xyz")` won't work if `vec`
+then you'll only be able to call `const` methods through `operator->`. 
+So, for example, `vec->push_back("xyz")` won't work if `vec`

 were `const`-qualified. The locking mechanism capitalizes on the
 assumption that `const` methods don't modify their underlying
 data and only acquires a read lock (as opposed to a read and
 were `const`-qualified. The locking mechanism capitalizes on the
 assumption that `const` methods don't modify their underlying
 data and only acquires a read lock (as opposed to a read and