diff options
| author | Jon Atack <jonnyatack@gmail.com> | 2015-04-15 11:43:14 +0530 |
|---|---|---|
| committer | Jon Atack <jonnyatack@gmail.com> | 2015-04-15 16:25:24 +0530 |
| commit | 6345f31fbfb4a683f98a3d13dc73c20533d0e0b7 (patch) | |
| tree | f561a448d482cf37d08496a761a945f1c18f696e /guides/source/i18n.md | |
| parent | 163de75707dc41924003fb938eb9db61efda9cf1 (diff) | |
| download | rails-6345f31fbfb4a683f98a3d13dc73c20533d0e0b7.tar.gz rails-6345f31fbfb4a683f98a3d13dc73c20533d0e0b7.tar.bz2 rails-6345f31fbfb4a683f98a3d13dc73c20533d0e0b7.zip | |
Fix typos and improve the documentation
This is a squash of the following commits, from first to last:
-
Fix minor, random things I’ve come across lately that individually
did not seem worth making a PR for, so I saved them for one commit.
One common error is using “it’s” (which is an abbreviation of “it is”)
when the possessive “its” should be used for indicating possession.
-
Changes include the name of a test, so remove the `[skip ci]` (thanks @senny).
-
Line wrap the changes at 80 chars and add one more doc fix.
-
Add a missing line wrap in the Contributing to Ruby on Rails Guide.
-
Line wrap the `TIP` section in the Contributing to Ruby on Rails Guide as well.
Rendering the guide locally with `bundle exec rake guides:generate` did
not show any change in on-screen formatting after adding the line wrap.
The HTML generated is (extra line added to illustrate where the line
wrap takes place):
<div class="info"><p>Please squash your commits into a single commit
when appropriate. This
simplifies future cherry picks and also keeps the git log
clean.</p></div>
-
Squash commits.
Diffstat (limited to 'guides/source/i18n.md')
| -rw-r--r-- | guides/source/i18n.md | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/guides/source/i18n.md b/guides/source/i18n.md index 27f11ebbee..348c60a9d8 100644 --- a/guides/source/i18n.md +++ b/guides/source/i18n.md @@ -489,7 +489,9 @@ NOTE: The default locale loading mechanism in Rails does not load locale files i Overview of the I18n API Features --------------------------------- -You should have good understanding of using the i18n library now, knowing all necessary aspects of internationalizing a basic Rails application. In the following chapters, we'll cover it's features in more depth. +You should have a good understanding of using the i18n library now and know how +to internationalize a basic Rails application. In the following chapters, we'll +cover its features in more depth. These chapters will show examples using both the `I18n.translate` method as well as the [`translate` view helper method](http://api.rubyonrails.org/classes/ActionView/Helpers/TranslationHelper.html#method-i-translate) (noting the additional feature provide by the view helper method). |