Skip to content
This repository
Browse code

As we have moved to rails/docrails from lifo/docrails

Changing links to guides.

We are not worried for old versions as GitHub is 
handling the redirects.
  • Loading branch information...
commit f8005de530fd73121046672435be49e714d528c6 1 parent 7d40aa4
Arun Agrawal authored June 06, 2013
4  guides/source/contributing_to_ruby_on_rails.md
Source Rendered
@@ -182,9 +182,9 @@ Contributing to the Rails Documentation
182 182
 
183 183
 Ruby on Rails has two main sets of documentation: the guides help you in learning about Ruby on Rails, and the API is a reference.
184 184
 
185  
-You can help improve the Rails guides by making them more coherent, consistent or readable, adding missing information, correcting factual errors, fixing typos, or bringing it up to date with the latest edge Rails. To get involved in the translation of Rails guides, please see [Translating Rails Guides](https://wiki.github.com/lifo/docrails/translating-rails-guides).
  185
+You can help improve the Rails guides by making them more coherent, consistent or readable, adding missing information, correcting factual errors, fixing typos, or bringing it up to date with the latest edge Rails. To get involved in the translation of Rails guides, please see [Translating Rails Guides](https://wiki.github.com/rails/docrails/translating-rails-guides).
186 186
 
187  
-If you're confident about your changes, you can push them directly yourself via [docrails](https://github.com/lifo/docrails). Docrails is a branch with an **open commit policy** and public write access. Commits to docrails are still reviewed, but this happens after they are pushed. Docrails is merged with master regularly, so you are effectively editing the Ruby on Rails documentation.
  187
+If you're confident about your changes, you can push them directly yourself via [docrails](https://github.com/rails/docrails). Docrails is a branch with an **open commit policy** and public write access. Commits to docrails are still reviewed, but this happens after they are pushed. Docrails is merged with master regularly, so you are effectively editing the Ruby on Rails documentation.
188 188
 
189 189
 If you are unsure of the documentation changes, you can create an issue in the [Rails](https://github.com/rails/rails/issues) issues tracker on GitHub.
190 190
 
2  guides/source/getting_started.md
Source Rendered
@@ -64,7 +64,7 @@ Creating a New Rails Project
64 64
 The best way to use this guide is to follow each step as it happens, no code or
65 65
 step needed to make this example application has been left out, so you can
66 66
 literally follow along step by step. You can get the complete code
67  
-[here](https://github.com/lifo/docrails/tree/master/guides/code/getting_started).
  67
+[here](https://github.com/rails/docrails/tree/master/guides/code/getting_started).
68 68
 
69 69
 By following along with this guide, you'll create a Rails project called
70 70
 `blog`, a
4  guides/source/layout.html.erb
@@ -102,10 +102,10 @@
102 102
         </p>
103 103
         <p>
104 104
           If you see any typos or factual errors you are confident to
105  
-          patch, please clone <%= link_to 'docrails', 'https://github.com/lifo/docrails' %>
  105
+          patch, please clone <%= link_to 'docrails', 'https://github.com/rails/docrails' %>
106 106
           and push the change yourself. That branch of Rails has public write access.
107 107
           Commits are still reviewed, but that happens after you've submitted your
108  
-          contribution. <%= link_to 'docrails', 'https://github.com/lifo/docrails' %> is
  108
+          contribution. <%= link_to 'docrails', 'https://github.com/rails/docrails' %> is
109 109
           cross-merged with master periodically.
110 110
         </p>
111 111
         <p>

0 notes on commit f8005de

Please sign in to comment.
Something went wrong with that request. Please try again.