edits from AS

Author: genwhittTTD

docs/getting-started/gs-credentials.md

@@ -42,7 +42,7 @@ Notes:
 If you're using a client-server or server-side implementation (see [UID2 Client-Server Integration Guide for Prebid.js](../guides/integration-prebid-client-server.md) or [Client-Server Integration Guide for JavaScript](../guides/integration-javascript-client-server.md)), the API key and client secret allow you to connect to the <Link href="../ref-info/glossary-uid#gl-operator-service">Operator Service</Link> and call API endpoints. These values identify you to the service.
 
 Here is some information about API keys and client secrets:
-- It's important that you keep these values secure. For details, see [Security of API Key and Client Secret](#security-of-api-key-and-client-secret).
+- You must keep these values secure. For details, see [Security of API Key and Client Secret]
 - One UID2 participant can have multiple keys.
 - Each key has a set of [permissions](gs-permissions.md) that determine the endpoints you can use it on.
 - Each key has a corresponding client secret.

docs/portal/api-keys.md

@@ -10,7 +10,7 @@ import Link from '@docusaurus/Link';
 # API Keys
 
 :::note
-These instructions are for client-server or server-side implementations. If your UID2 implementation will be client-side, you'll need to set up different values. For details, see [Client-Side Integration](client-side-integrations.md).
+These instructions are for client-server or server-side implementations. If your UID2 implementation will be client-side, or visible to the public in any way, you'll need to set up different values. For details, see [Client-Side Integration](client-side-integrations.md).
 :::
 
 In the UID2 Portal, on the **API Keys** page, you can perform all activities relating to managing the API keys for your UID2 account, including the following: