@@ -27,7 +27,7 @@ out of the box in most modern browsers (old versions of Edge and IE require
27
27
languages.
28
28
29
29
Mercure comes with an authorization mechanism,
30
- automatic re-connection in case of network issues
30
+ automatic reconnection in case of network issues
31
31
with retrieving of lost updates, a presence API,
32
32
"connection-less" push for smartphones and auto-discoverability (a supported
33
33
client can automatically discover and subscribe to updates of a given resource
@@ -84,7 +84,7 @@ and a managed, High Availability Hub are also provided.
84
84
Configuration
85
85
-------------
86
86
87
- The preferred way to configure the MercureBundle is using
87
+ The preferred way to configure MercureBundle is using
88
88
:doc: `environment variables </configuration >`.
89
89
90
90
When MercureBundle has been installed, the ``.env `` file of your project
@@ -97,7 +97,7 @@ and you can skip straight to the next section.
97
97
Otherwise, set the URL of your hub as the value of the ``MERCURE_URL ``
98
98
and ``MERCURE_PUBLIC_URL `` env vars.
99
99
Sometimes a different URL must be called by the Symfony app (usually to publish),
100
- and the JavaScript client (usually to subscrribe ). It's especially common when
100
+ and the JavaScript client (usually to subscribe ). It's especially common when
101
101
the Symfony app must use a local URL and the client-side JavaScript code a public one.
102
102
In this case, ``MERCURE_URL `` must contain the local URL that will be used by the
103
103
Symfony app (e.g. ``https://mercure/.well-known/mercure ``), and ``MERCURE_PUBLIC_URL ``
@@ -297,7 +297,7 @@ and to subscribe to it:
297
297
Authorization
298
298
-------------
299
299
300
- Mercure also allows to dispatch updates only to authorized clients.
300
+ Mercure also allows dispatching updates only to authorized clients.
301
301
To do so, mark the update as **private ** by setting the third parameter
302
302
of the ``Update `` constructor to ``true ``::
303
303
@@ -348,7 +348,7 @@ is the way to go.
348
348
.. tip ::
349
349
350
350
The native implementation of EventSource doesn't allow specifying headers.
351
- For example, authorization using Bearer token. In order to achieve that, use `a polyfill `_
351
+ For example, authorization using a Bearer token. In order to achieve that, use `a polyfill `_
352
352
353
353
.. code-block :: javascript
354
354
@@ -559,7 +559,7 @@ its Mercure support.
559
559
Testing
560
560
--------
561
561
562
- During unit testing there is not need to send updates to Mercure.
562
+ During unit testing there is no need to send updates to Mercure.
563
563
564
564
You can instead make use of the `MockHub `::
565
565
0 commit comments