diff options
| author | Anton Davydov <antondavydov.o@gmail.com> | 2015-03-15 23:55:06 +0300 |
|---|---|---|
| committer | Anton Davydov <antondavydov.o@gmail.com> | 2015-03-15 23:55:06 +0300 |
| commit | a2902941757f8abfaba8927410bba7f27020fbfb (patch) | |
| tree | 1d3ec288c3aaeae0a174ced22a6ea12a4344479c /guides | |
| parent | 575839d75fa85731facb99489e53b45f5f041b51 (diff) | |
| download | rails-a2902941757f8abfaba8927410bba7f27020fbfb.tar.gz rails-a2902941757f8abfaba8927410bba7f27020fbfb.tar.bz2 rails-a2902941757f8abfaba8927410bba7f27020fbfb.zip | |
[skip ci] Fix typos in guides
Diffstat (limited to 'guides')
| -rw-r--r-- | guides/source/active_record_querying.md | 2 | ||||
| -rw-r--r-- | guides/source/asset_pipeline.md | 2 |
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 |