fix: <!-- not displayed in docs after changes

Author: rameziophobia

docs/javascript/code-splitting.md

@@ -16,7 +16,7 @@ Let's say you're requesting a page that needs to fetch a code chunk from the ser
 
 > Warning: React attempted to reuse markup in a container but the checksum was invalid. This generally means that you are using server rendering and the markup generated on the server was not what the client was expecting. React injected new markup to compensate which works but you have lost many of the benefits of server rendering. Instead, figure out why the markup being generated is different on the client or server:
 
-> (client) `react-empty: 1 -`
+> (client) `<!-- react-empty: 1 -`
 
 > (server) `<div data-reactroot="`
 

docs/outdated/deferred-rendering.md

@@ -18,7 +18,6 @@ Let's say you're requesting a page that needs to fetch a code chunk from the ser
 > (client) `<!-- react-empty: 1 -`
 
 > (server) `<div data-reactroot="`
-<!--This comment is here because the comment beginning on line 13 messes up Sublime's markdown parsing-->
 
 Different markup is generated on the client than on the server. Why does this happen? When you register a component or Render-Function with `ReactOnRails.register`, React on Rails will by default render the component as soon as the page loads. However, code splitting requires that components render at a later time when the JavaScript chunks have loaded.