Update browser-sdk-2.md

content/collections/browser_sdk/en/browser-sdk-2.md

@@ -1130,7 +1130,7 @@ Unlike standard network requests, sendBeacon sends events in the background, eve
 `sendBeacon` sends events in the background. As a result, events dispatched by `sendBeacon` don't return server responses. Keep the following in mind if you use `sendBeacon`:
 
 1. Requests are not retried, including failed requests with 4xx or 5xx responses, so events may be lost.
-2. Event order cannot be guaranteed, as `sendBeacon` may send events in parallel. This can lead to some UTM properties not being set, e.g. for session start events. In contrast, while using `fetch`, the SDK waits for responses before proceeding, guaranteeing event order.
+2. Event order cannot be guaranteed, as `sendBeacon` may send events in parallel. This can lead to some UTM properties not being set, for example for session start events. In contrast, while using `fetch`, the SDK waits for responses before proceeding, guaranteeing event order.
 {{/partial:admonition}}
 
 #### Set the transport to use sendBeacon for all events