From f5000c63477333ffcd319aa8f020adbd0ec657f8 Mon Sep 17 00:00:00 2001
From: Jennifer Long <30329756+MrsLong@users.noreply.github.com>
Date: Sat, 6 Apr 2024 10:04:22 -0500
Subject: [PATCH] Update routing.md

Added "is" for clarity in the opening sentence.
---
 src/guide/scaling-up/routing.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/src/guide/scaling-up/routing.md b/src/guide/scaling-up/routing.md
index 6b7b693d04..4cc26f6e83 100644
--- a/src/guide/scaling-up/routing.md
+++ b/src/guide/scaling-up/routing.md
@@ -2,7 +2,7 @@
 
 ## Client-Side vs. Server-Side Routing {#client-side-vs-server-side-routing}
 
-Routing on the server side means the server sending a response based on the URL path that the user is visiting. When we click on a link in a traditional server-rendered web app, the browser receives an HTML response from the server and reloads the entire page with the new HTML.
+Routing on the server side means the server is sending a response based on the URL path that the user is visiting. When we click on a link in a traditional server-rendered web app, the browser receives an HTML response from the server and reloads the entire page with the new HTML.
 
 In a [Single-Page Application](https://developer.mozilla.org/en-US/docs/Glossary/SPA) (SPA), however, the client-side JavaScript can intercept the navigation, dynamically fetch new data, and update the current page without full page reloads. This typically results in a more snappy user experience, especially for use cases that are more like actual "applications", where the user is expected to perform many interactions over a long period of time.