@@ -312,18 +312,12 @@ as patterns:
312312
313313.. tip ::
314314
315- Google Chrome DevTools natively integrate a `practical UI `_ displaying in live
316- the received events:
315+ Google Chrome features a practical UI to display the received events:
317316
318317 .. image :: /_images/mercure/chrome.png
319318 :alt: The Chrome DevTools showing the EventStream tab containing information about each SSE event.
320319
321- To use it:
322-
323- * open the DevTools
324- * select the "Network" tab
325- * click on the request to the Mercure hub
326- * click on the "EventStream" sub-tab.
320+ In DevTools, select the "Network" tab, then click on the request to the Mercure hub, then on the "EventStream" sub-tab.
327321
328322Discovery
329323---------
@@ -676,7 +670,7 @@ sent:
676670 mercure.hub.default :
677671 class : App\Tests\Functional\Stub\HubStub
678672
679- As MercureBundle support multiple hubs, you may have to replace
673+ As MercureBundle supports multiple hubs, you may have to replace
680674the other service definitions accordingly.
681675
682676.. tip ::
@@ -766,7 +760,6 @@ Going further
766760.. _`JSON Web Token` : https://tools.ietf.org/html/rfc7519
767761.. _`example JWT` : https://jwt.io/#debugger-io?token=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJtZXJjdXJlIjp7InB1Ymxpc2giOlsiKiJdfX0.iHLdpAEjX4BqCsHJEegxRmO-Y6sMxXwNATrQyRNt3GY
768762.. _`IRI` : https://tools.ietf.org/html/rfc3987
769- .. _`practical UI` : https://twitter.com/ChromeDevTools/status/562324683194785792
770763.. _`the dedicated API Platform documentation` : https://api-platform.com/docs/core/mercure/
771764.. _`the online debugger` : https://uri-template-tester.mercure.rocks
772765.. _`a feature to test applications using Mercure` : https://github.com/symfony/panther#creating-isolated-browsers-to-test-apps-using-mercure-or-websocket
0 commit comments