Add links to lighthouse ticket for i18n guide

1 files changed, 3 insertions, 9 deletions

diff --git a/railties/doc/guides/html/i18n.html b/railties/doc/guides/html/i18n.html
index d4433451ba..8a6e4cc990 100644
--- a/railties/doc/guides/html/i18n.html
+++ b/railties/doc/guides/html/i18n.html
@@ -103,10 +103,7 @@
           <a href="#_footnotes">Footnotes</a>
           </li>
           <li>
-          <a href="#_credits">Credits</a>
-          </li>
-          <li>
-          <a href="#_notes">NOTES</a>
+          <a href="#_changelog">Changelog</a>
           </li>
       </ol>
     </div>
@@ -850,12 +847,9 @@ http://www.gnu.org/software/src-highlite -->
 <div class="paragraph"><p><a id="2"></a>[2] Other backends might allow or require to use other formats, e.g. a GetText backend might allow to read GetText files.</p></div>

 <div class="paragraph"><p><a id="3"></a>[3] One of these reasons is that we don&#8217;t want to any unnecessary load for applications that do not need any I18n capabilities, so we need to keep the I18n library as simple as possible for English. Another reason is that it is virtually impossible to implement a one-fits-all solution for all problems related to I18n for all existing languages. So a solution that allows us to exchange the entire implementation easily is appropriate anyway. This also makes it much easier to experiment with custom features and extensions.</p></div>

 </div>

-<h2 id="_credits">9. Credits</h2>

-<div class="sectionbody">

-</div>

-<h2 id="_notes">10. NOTES</h2>

+<h2 id="_changelog">9. Changelog</h2>

 <div class="sectionbody">

-<div class="paragraph"><p>How to contribute?</p></div>

+<div class="paragraph"><p><a href="http://rails.lighthouseapp.com/projects/16213/tickets/23">Lighthouse ticket</a></p></div>

 </div>

 
     </div>