Fix link and typos (#574)

Signed-off-by: Fabien Lavocat <4154532+FabienLavocat@users.noreply.github.com>

Author: FabienLavocat

millicast/distribution/access-control/allowed-origins.md

@@ -50,7 +50,7 @@ This access control method is not supported when using RTMP.
 
 ### Allowed IP addresses
 
-This approach allows for explicitly defining multiple _IPv4 addresses_ or \_Classless Inter-Domain Routing (CIDR) \_notated network blocks when creating or updating a token. A token will only be accepted when the requesting IP address originates from one of the network addresses that match.
+This approach allows for explicitly defining multiple _IPv4 addresses_ or _Classless Inter-Domain Routing (CIDR)_ notated network blocks when creating or updating a token. A token will only be accepted when the requesting IP address originates from one of the network addresses that match.
 
 _For example_, to allow only a specific person or persons to broadcast you would specify the publisher's IP address in this property. If you wanted only a specific organization to be able to watch, you might specify the series of IP addresses in a subscribe token so that content can only be viewed within a specific network.
 

millicast/playback/players-sdks/web/player/index.mdx

@@ -30,7 +30,7 @@ player.source = {
 
 ### Controlling ABR Strategies
 
-For greater control over how Adaptive Bitrate (ABR) behaves, applications can set the ABR strategies for WebRTC. This feature provides the ability to choose on a viewer-by-viewer basis how aggressively to apply ABR switching when ABR streaming is used. It is inline with [OptiView Player's existing strategies](https://docs.optiview.dolby.com/theoplayer/v9/api-reference/web/interfaces/ABRStrategyConfiguration.html). For now, users must set this value when choosing playback to utilize the feature, in the future we will set `quality` to be the default.
+For greater control over how Adaptive Bitrate (ABR) behaves, applications can set the ABR strategies for WebRTC. This feature provides the ability to choose on a viewer-by-viewer basis how aggressively to apply ABR switching when ABR streaming is used. It is inline with [OptiView Player's existing strategies](pathname:///theoplayer/v10/api-reference/web/interfaces/ABRStrategyConfiguration.html) . For now, users must set this value when choosing playback to utilize the feature, in the future we will set `quality` to be the default.
 
 The options are:
 

millicast/streaming-dashboard/subscribe-tokens.mdx

@@ -185,7 +185,7 @@ Examples of self-singing a token can be found at this [GitHub repository](https:
 
 - The published stream and Subscribe token **must** originate from the same cluster region. The "Auto" region may be selected for both if the broadcast region changes from stream to stream. For more information, see [Multi-region Support](/millicast/distribution/multi-region-support/index.mdx).
 - The only fields in the self-signed token that are added to the primary subscriber token are the _allowedOrigins_ and _allowedIPAddresses_. These do not replace any _allowedOrigins_ or _allowedIPAddresses_ in the primary Subscriber token but are appended onto any existing restrictions. **Anything else packaged into the JWT is ignored.**
-- If the primary Subscriber token contains a* TrackingID*, the self-signed token must use the same _TrackingID_. However, if the primary Subscriber token does not specify a _TrackingID_, any _TrackingID_ can be used in the self-signed token.
+- If the primary Subscriber token contains a _TrackingID_, the self-signed token must use the same _TrackingID_. However, if the primary Subscriber token does not specify a _TrackingID_, any _TrackingID_ can be used in the self-signed token.
 - The Stream name can differ in the self-signed token when using a regex value. If the primary Subscriber token doesn't validate the Stream name (via regex match) in the self-signed token, then it is rejected.
 - Self-signed tokens are **not revocable** and must be cycled if exposed.
 - If the parent Subscribe token has specific streams in it, then the self-signed Subscribe token must match one of them.