aboutsummaryrefslogtreecommitdiffstats
path: root/guides
diff options
context:
space:
mode:
authorXavier Noria <fxn@hashref.com>2015-03-15 22:02:28 +0100
committerXavier Noria <fxn@hashref.com>2015-03-15 22:02:28 +0100
commita5a4b56029f1a83cfc81852f8ca76f9161abcbaa (patch)
tree3972e2c97d8d46eed2c0497ba34e66cfce5e1cf8 /guides
parent341ee0fde1ca1dc7c626311ecc31ac43f28225d8 (diff)
parenta2902941757f8abfaba8927410bba7f27020fbfb (diff)
downloadrails-a5a4b56029f1a83cfc81852f8ca76f9161abcbaa.tar.gz
rails-a5a4b56029f1a83cfc81852f8ca76f9161abcbaa.tar.bz2
rails-a5a4b56029f1a83cfc81852f8ca76f9161abcbaa.zip
Merge pull request #19345 from davydovanton/doc-fix-spell-guides
[skip ci] Fix typos in guides
Diffstat (limited to 'guides')
-rw-r--r--guides/source/active_record_querying.md2
-rw-r--r--guides/source/asset_pipeline.md2
2 files changed, 2 insertions, 2 deletions
diff --git a/guides/source/active_record_querying.md b/guides/source/active_record_querying.md
index e5a962b739..bef903b751 100644
--- a/guides/source/active_record_querying.md
+++ b/guides/source/active_record_querying.md
@@ -348,7 +348,7 @@ Another example would be if you wanted multiple workers handling the same proces
Similar to the `:begin_at` option, `:end_at` allows you to configure the last ID of the sequence whenever the highest ID is not the one you need.
This would be useful, for example, if you wanted to run a batch process, using a subset of records based on `:begin_at` and `:end_at`
-For example, to send newsletters only to users with the primary key starting from 2000 upto 10000 and to retrieve them in batches of 1000:
+For example, to send newsletters only to users with the primary key starting from 2000 up to 10000 and to retrieve them in batches of 1000:
```ruby
User.find_each(begin_at: 2000, end_at: 10000, batch_size: 5000) do |user|
diff --git a/guides/source/asset_pipeline.md b/guides/source/asset_pipeline.md
index da347ef344..c9ae256c83 100644
--- a/guides/source/asset_pipeline.md
+++ b/guides/source/asset_pipeline.md
@@ -921,7 +921,7 @@ focus on serving application code as fast as possible.
#### Set up a CDN to Serve Static Assets
To set up your CDN you have to have your application running in production on
-the internet at a publically available URL, for example `example.com`. Next
+the internet at a publicly available URL, for example `example.com`. Next
you'll need to sign up for a CDN service from a cloud hosting provider. When you
do this you need to configure the "origin" of the CDN to point back at your
website `example.com`, check your provider for documentation on configuring the