From b956b66599e5ed6b55dc7a1d06d15efada8c67b8 Mon Sep 17 00:00:00 2001
From: Polaris <37720445+PolarisWasInDenial@users.noreply.github.com>
Date: Thu, 18 Jul 2024 02:09:55 -0500
Subject: [PATCH] Update cms.md

---
 docs/en/guide/cms.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/en/guide/cms.md b/docs/en/guide/cms.md
index 8694cf0a..d4f1b01d 100644
--- a/docs/en/guide/cms.md
+++ b/docs/en/guide/cms.md
@@ -10,7 +10,7 @@ Connecting VitePress to a CMS will largely revolve around [Dynamic Routes](./rou
 
 Since each CMS will work differently, here we can only provide a generic workflow that you will need to adapt to your specific scenario.
 
-1. If your CMS requires authentication, create an `.env` file to store your API tokens and load it so:
+1. If your CMS requires authentication, create a `.env` file to store your API tokens and load it so:
 
     ```js
     // posts/[id].paths.js
@@ -41,7 +41,7 @@ Since each CMS will work differently, here we can only provide a generic workflo
     }
     ```
 
-3. Render the content in the page:
+3. Render the content on the page:
 
     ```md
     # {{ $params.title }}