@@ -174,7 +174,7 @@ paths](#digested-assets-in-views) using helpers like `asset_path`, `image_tag`,
174
174
automatically converted into their fingerprinted paths using the
175
175
[ ` .manifest.json ` file] ( #manifest-files ) .
176
176
177
- Its possible to exclude certain directories from this process, you can read more
177
+ It is possible to exclude certain directories from this process, you can read more
178
178
about it in the [ Fingerprinting
179
179
section] ( #fingerprinting-versioning-with-digest-based-urls ) .
180
180
@@ -359,7 +359,7 @@ serve them efficiently.
359
359
360
360
### Setup
361
361
362
- Follow these steps for setup Propshaft in your Rails application:
362
+ Follow these steps for setting up Propshaft in your Rails application:
363
363
364
364
1 . Create a new Rails application:
365
365
@@ -542,7 +542,7 @@ headers.
542
542
For Apache:
543
543
544
544
```apache
545
- # The Expires* directives requires the Apache module
545
+ # The Expires* directives require the Apache module
546
546
# `mod_expires` to be enabled.
547
547
<Location /assets/>
548
548
# Use of ETag is discouraged when Last-Modified is present
@@ -642,7 +642,7 @@ it will try to find it at the "origin" `example.com/assets/smile.png`, and then
642
642
store it for future use.
643
643
644
644
If you want to serve only some assets from your CDN, you can use custom ` :host`
645
- option your asset helper, which overwrites value set in
645
+ option for your asset helper, which overwrites the value set in
646
646
[` config.action_controller.asset_host` ][].
647
647
648
648
` ` ` erb
@@ -1013,7 +1013,7 @@ delivered via the Rails asset pipeline.
1013
1013
4. In production, the gem ensures your stylesheets are compiled and ready for
1014
1014
deployment. During the `assets:precompile` step, it installs all
1015
1015
`package.json` dependencies via `bun`, `yarn`, `pnpm` or `npm` and runs the
1016
- `build:css` task. to process your stylesheet entry points. The resulting CSS
1016
+ `build:css` task to process your stylesheet entry points. The resulting CSS
1017
1017
output is then digested by the asset pipeline and copied into the
1018
1018
`public/assets` directory, just like other asset pipeline files.
1019
1019
0 commit comments