<?xml version="1.0" encoding="UTF-8"?>
<commit>
  <added type="array"/>
  <modified type="array">
    <modified>
      <diff>@@ -65,9 +65,9 @@ about `ActiveReload::ConnectionProxy` and abort. A possible workaround is to mon
       end
     end
 
-### Litespeed web server or Phusion Passenger (mod_rails)
+### Litespeed web server or Phusion Passenger (mod\_rails)
 
-If you are using the Litespeed web server or Passenger (mod_rails), child processes are initialized on creation,
+If you are using the Litespeed web server or Passenger (mod\_rails), child processes are initialized on creation,
 which means any setup done in an environment file will be effectively ignored. [A brief
 discussion of the problem is posted here](http://litespeedtech.com/support/wiki/doku.php?id=litespeed_wiki:rails:memcache).
 
@@ -85,10 +85,10 @@ the `setup!` call if your connection hasn't been initialized, like:
 Advanced
 --------
 
-The ActiveReload::MasterDatabase model uses a 'master_database' setting that can either be
+The ActiveReload::MasterDatabase model uses a 'master\_database' setting that can either be
 defined for all of your environments, or for each environment as a nested declaration.
 
-The ActiveReload::SlaveDatabase model uses a 'slave_database' setting that can only be
+The ActiveReload::SlaveDatabase model uses a 'slave\_database' setting that can only be
 defined per environment.
 
 Example:</diff>
      <filename>README.markdown</filename>
    </modified>
  </modified>
  <removed type="array"/>
  <parents type="array">
    <parent>
      <id>eacc03d05eeef76af817b086552f319a4705816c</id>
    </parent>
  </parents>
  <author>
    <name>CORP\thanley</name>
    <email>corpthanley@mtvl08w001094.(none)</email>
  </author>
  <url>http://github.com/technoweenie/masochism/commit/7d07347a2eafea5d8b51452f7a33ba25dd8e6f7a</url>
  <id>7d07347a2eafea5d8b51452f7a33ba25dd8e6f7a</id>
  <committed-date>2009-01-11T21:17:07-08:00</committed-date>
  <authored-date>2009-01-06T21:42:44-08:00</authored-date>
  <message>Fixed some markdown syntax

Signed-off-by: rick &lt;technoweenie@gmail.com&gt;</message>
  <tree>497ad4ce7fc04ca39ab45a433b7b094bb834a4fe</tree>
  <committer>
    <name>rick</name>
    <email>technoweenie@gmail.com</email>
  </committer>
</commit>
