From 1109c0e70e027fa7502ab3f0130ba3af77780d68 Mon Sep 17 00:00:00 2001
From: Polaris <37720445+PolarisWasInDenial@users.noreply.github.com>
Date: Thu, 18 Jul 2024 03:24:58 -0500
Subject: [PATCH] Update ssr-compat.md

---
 docs/en/guide/ssr-compat.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/en/guide/ssr-compat.md b/docs/en/guide/ssr-compat.md
index a7a447d1..8f2d9d40 100644
--- a/docs/en/guide/ssr-compat.md
+++ b/docs/en/guide/ssr-compat.md
@@ -4,7 +4,7 @@ outline: deep
 
 # SSR Compatibility
 
-VitePress pre-renders the app in Node.js during the production build, using Vue's Server-Side Rendering (SSR) capabilities. This means all custom code in theme components are subject to SSR Compatibility.
+VitePress pre-renders the app in Node.js during the production build, using Vue's Server-Side Rendering (SSR) capabilities. This means all custom code in theme components is subject to SSR Compatibility.
 
 The [SSR section in official Vue docs](https://vuejs.org/guide/scaling-up/ssr.html) provides more context on what SSR is, the relationship between SSR / SSG, and common notes on writing SSR-friendly code. The rule of thumb is to only access browser / DOM APIs in `beforeMount` or `mounted` hooks of Vue components.