8000 minor #10493 Some punctuation not properly placed (hktr92) · symfony/symfony-docs@12b2f02 · GitHub
[go: up one dir, main page]

Skip to content

Commit 12b2f02

Browse files
committed
minor #10493 Some punctuation not properly placed (hktr92)
This PR was merged into the 4.1 branch. Discussion ---------- Some punctuation not properly placed While reading this documentation, I felt like some punctuation was not properly placed, so I changed them a little. Commits ------- d4fcbac Some punctuation stuff
2 parents d372739 + d4fcbac commit 12b2f02

File tree

1 file changed

+4
-4
lines changed

1 file changed

+4
-4
lines changed

frontend/encore/simple-example.rst

Lines changed: 4 additions & 4 deletions
< 8CF6 tr class="diff-line-row">
Original file line numberDiff line numberDiff line change
@@ -98,7 +98,7 @@ your layout. In Symfony, use the ``asset()`` helper:
9898
Requiring JavaScript Modules
9999
----------------------------
100100

101-
Webpack is a module bundler... which means that you can ``require`` other JavaScript
101+
Webpack is a module bundler, which means that you can ``require`` other JavaScript
102102
files. First, create a file that exports a function:
103103

104104
.. code-block:: javascript
@@ -139,9 +139,9 @@ The import and export Statements
139139

140140
Instead of using ``require`` and ``module.exports`` like shown above, JavaScript
141141
has an alternate syntax, which is a more accepted standard. Choose whichever you
142-
want: they function identically:
142+
want, they function identically.
143143

144-
To export values, use ``exports``:
144+
To export values using the alternate syntax, use ``exports``:
145145

146146
.. code-block:: diff
147147
@@ -168,7 +168,7 @@ Page-Specific JavaScript or CSS (Multiple Entries)
168168
--------------------------------------------------
169169

170170
So far, you only have one final JavaScript file: ``app.js``. For simple apps or
171-
SPA's (Single Page Applications), that might be fine! However, as your app grows,
171+
SPAs (Single Page Applications), that might be fine! However, as your app grows,
172172
you may want to have page-specific JavaScript or CSS (e.g. homepage, blog, store,
173173
etc.). To handle this, add a new "entry" for each page that needs custom JavaScript
174174
or CSS:

0 commit comments

Comments
 (0)
0