Apply suggestions from code review

Co-authored-by: Aditya Oberai <adityaoberai1@gmail.com>

Author: atharvadeosthale

src/routes/blog/post/announcing-api-keys-api/+page.markdoc

@@ -13,11 +13,11 @@ callToAction: true
 
 Managing API keys has always required navigating to the Appwrite Console, selecting scopes, and manually creating each key. For a single project, that works. For teams managing multiple environments, onboarding new services, or provisioning keys as part of automated pipelines, it becomes a bottleneck.
 
-Today, we are announcing the **Keys API**, allowing you to create, update, and delete API keys programmatically through the Appwrite Server SDKs.
+Today, we are announcing the **Keys API**, allowing you to create, update, and delete API keys programmatically through the Appwrite server SDKs.
 
 # Why this matters
 
-API keys are the foundation of server-side authentication in Appwrite. Every Server SDK call, every CLI operation, and every backend integration depends on them. Being able to manage keys from code opens up workflows that were previously manual:
+API keys are the foundation of server-side authentication in Appwrite. Every server SDK call, every CLI operation, and every backend integration depends on them. Being able to manage keys from code opens up workflows that were previously manual:
 
 - **CI/CD pipelines** that provision scoped keys for each deployment environment
 - **Multi-tenant platforms** that create isolated keys per customer with only the scopes they need

src/routes/changelog/(entries)/2026-04-14.markdoc

@@ -5,7 +5,7 @@ date: 2026-04-14
 cover: /images/blog/improve-devex-dev-keys/cover.png
 ---
 
-API keys can now be created, updated, and deleted programmatically using the Appwrite Server SDKs. Two new API key scopes, `keys.read` and `keys.write`, control access to the new endpoints.
+API keys can now be created, updated, and deleted programmatically using the Appwrite server SDKs. Two new API key scopes, `keys.read` and `keys.write`, control access to the new endpoints.
 
 This enables automated key provisioning for CI/CD pipelines, multi-tenant platforms, key rotation workflows, and any scenario where managing keys through the Console is not practical.