AWS ivs: Fix IVS API reference URLs
Summary
Corrected broken links to IVS API documentation by removing extra slashes.
Security assessment
URL fixes don't alter security practices or address vulnerabilities; purely cosmetic.
Evidence
+This integration requires endpoints on your server that talk to the [Amazon IVS API](https://docs.aws.amazon.com/ivs/latest/LowLatencyAPIReference/Welcome.html).
Diff
diff --git a/ivs/latest/ChatUserGuide/chat-android-getting-started.md b/ivs/latest/ChatUserGuide/chat-android-getting-started.md index 2b8892e16..db24dd992 100644 --- a//ivs/latest/ChatUserGuide/chat-android-getting-started.md +++ b//ivs/latest/ChatUserGuide/chat-android-getting-started.md @@ -32 +32 @@ Add the following entries to your R8/Proguard rules file (`proguard-rules.pro`): -This integration requires endpoints on your server that talk to the [Amazon IVS API](https://docs.aws.amazon.com//ivs/latest/LowLatencyAPIReference/Welcome.html). Use the [official AWS libraries](https://aws.amazon.com/developer/tools/) for access to the Amazon IVS API from your server. These are accessible within several languages from the public packages; e.g., node.js and Java. +This integration requires endpoints on your server that talk to the [Amazon IVS API](https://docs.aws.amazon.com/ivs/latest/LowLatencyAPIReference/Welcome.html). Use the [official AWS libraries](https://aws.amazon.com/developer/tools/) for access to the Amazon IVS API from your server. These are accessible within several languages from the public packages; e.g., node.js and Java. @@ -34 +34 @@ This integration requires endpoints on your server that talk to the [Amazon IVS -Next, create a server endpoint that talks to the [Amazon IVS Chat API](https://docs.aws.amazon.com//ivs/latest/ChatAPIReference/Welcome.html) and creates a token. +Next, create a server endpoint that talks to the [Amazon IVS Chat API](https://docs.aws.amazon.com/ivs/latest/ChatAPIReference/Welcome.html) and creates a token.