Address coderabbit concerns

src/pages/agent-network/connect-agents.mdx

@@ -5,7 +5,7 @@ export const description =
 
 # Connect Agents
 
-**Connect Agent** is the self-service page each user configures their own tools from. It
+**Connect Agents** is the self-service page each user configures their own tools from. It
 carries the account's [keyless endpoint](/agent-network/providers#the-keyless-endpoint), a
 ready-made configuration snippet for common agent tools, and the providers and models the
 user's own policies allow.

src/pages/agent-network/providers.mdx

@@ -146,12 +146,13 @@ picker.
 
 That matters differently per provider:
 
-- **AWS Bedrock** — models are region-scoped inference profiles whose ids carry a geography
-  prefix, such as `eu.anthropic.claude-sonnet-4-5-20250929-v1:0`. Only the exact id AWS
-  issues works at invoke time, and which ones exist depends on your account and region, so
-  there is nothing for a shipped catalog to list.
-- **Google Vertex AI** — models are enabled per project and region, so two projects with the
-  same key material expose different lists.
+- **AWS Bedrock** — some ids invoke a foundation model directly in your Region, such as
+  `anthropic.claude-sonnet-4-5-20250929-v1:0`, while others are cross-Region inference
+  profiles carrying a geography prefix like `eu.`, `us.`, or `global.`. Only the exact id
+  AWS issues works at invoke time, and which ids your credential can use depends on your
+  account and region, so a shipped catalog cannot know your line-up.
+- **Google Vertex AI** — discovery returns the publisher's global model list; invoking a
+  listed model can still be rejected if the configured project does not have access to it.
 - **OpenAI** and **Anthropic** — the public line-up is in the catalog, but an organization's
   access is not: preview and early-access models never appear, and models retired since your
   NetBird release still do.

src/pages/agent-network/quickstart.mdx

@@ -95,7 +95,7 @@ Point your agent at the NetBird endpoint as its **base URL**. No provider API ke
 is needed on the client. NetBird authorizes each request against your policies and
 injects the upstream provider key server-side.
 
-1. Go to **Agent Network > Connect Agent**. Every account member has this page, and it
+1. Go to **Agent Network > Connect Agents**. Every account member has this page, and it
    shows the endpoint along with the providers their own policies allow.
 2. Pick the tab that matches your tool, Claude Code, Codex, OpenAI SDK, or cURL. The
    dashboard pre-fills your endpoint for you.