diff --git a/src/content/changelogs-next/2025-01-26-worker-binding-methods.mdx b/src/content/changelogs-next/2025-01-26-worker-binding-methods.mdx
index e1cec9a2b2d300f..b2aca8abfe8569a 100644
--- a/src/content/changelogs-next/2025-01-26-worker-binding-methods.mdx
+++ b/src/content/changelogs-next/2025-01-26-worker-binding-methods.mdx
@@ -6,7 +6,7 @@ products:
 date: 2025-01-30T14:00:00Z
 ---
 
-We have released new,[Workers bindings API](/ai-gateway/integrations/worker-binding-methods/), allowing you to connect Workers applications to AI Gateway directly. These methods simplify how Workers calls AI services behind your AI Gateway configurations, removing the need to use the REST API and manually authenticate.
+We have released new [Workers bindings API methods](/ai-gateway/integrations/worker-binding-methods/), allowing you to connect Workers applications to AI Gateway directly. These methods simplify how Workers calls AI services behind your AI Gateway configurations, removing the need to use the REST API and manually authenticate.
 
 To add an AI binding to your Worker, include the following in your `wrangler.toml` or `wrangler.json` file:
 
@@ -16,7 +16,7 @@ With the new AI Gateway binding methods, you can now:
 
 - Send feedback and update metadata with `patchLog`.
 - Retrieve detailed log information using `getLog`.
-- Execute universal requests to any AI Gateway provider with `run`.
+- Execute [universal requests](/ai-gateway/providers/universal/) to any AI Gateway provider with `run`.
 
 For example, to send feedback and update metadata using `patchLog`: