From 96c34d75daa9bfd38f8ed56605c8ce4a05b6c6d3 Mon Sep 17 00:00:00 2001
From: Cassidy Williams <1454517+cassidoo@users.noreply.github.com>
Date: Thu, 20 Jul 2023 15:35:38 -0500
Subject: [PATCH 1/2] Change "publically" to "publicly" in the routing docs

---
 docs/02-app/01-building-your-application/01-routing/index.mdx | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/02-app/01-building-your-application/01-routing/index.mdx b/docs/02-app/01-building-your-application/01-routing/index.mdx
index 06118147f65fe..fbab832afa0d9 100644
--- a/docs/02-app/01-building-your-application/01-routing/index.mdx
+++ b/docs/02-app/01-building-your-application/01-routing/index.mdx
@@ -134,7 +134,7 @@ In a nested route, the components of a segment will be nested **inside** the com
 
 In addition to special files, you have the option to colocate your own files (e.g. components, styles, tests, etc) inside folders in the `app` directory.
 
-This is because while folders define routes, only the contents returned by `page.js` or `route.js` are publically addressable.
+This is because while folders define routes, only the contents returned by `page.js` or `route.js` are publicly addressable.
 
 <Image
   alt="An example folder structure with colocated files"

From 690340ede0ba4e346eac6e4bb5faddbd550ccf9b Mon Sep 17 00:00:00 2001
From: Cassidy Williams <1454517+cassidoo@users.noreply.github.com>
Date: Thu, 20 Jul 2023 15:39:19 -0500
Subject: [PATCH 2/2] Change "publically" to "publicly" in the colocation docs

---
 .../01-routing/12-colocation.mdx                          | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/docs/02-app/01-building-your-application/01-routing/12-colocation.mdx b/docs/02-app/01-building-your-application/01-routing/12-colocation.mdx
index 2585ce2c2a4c9..690af8e3b1649 100644
--- a/docs/02-app/01-building-your-application/01-routing/12-colocation.mdx
+++ b/docs/02-app/01-building-your-application/01-routing/12-colocation.mdx
@@ -24,20 +24,20 @@ In the `app` directory, [nested folder hierarchy](/docs/app/building-your-applic
 
 Each folder represents a route segment that is mapped to a corresponding segment in a URL path.
 
-However, even though route structure is defined through folders, a route is **not publically accessible** until a `page.js` or `route.js` file is added to a route segment.
+However, even though route structure is defined through folders, a route is **not publicly accessible** until a `page.js` or `route.js` file is added to a route segment.
 
 <Image
-  alt="A diagram showing how a route is not publically accessible until a page.js or route.js file is added to a route segment."
+  alt="A diagram showing how a route is not publicly accessible until a page.js or route.js file is added to a route segment."
   srcLight="/docs/light/project-organization-not-routable.png"
   srcDark="/docs/dark/project-organization-not-routable.png"
   width="1600"
   height="444"
 />
 
-And, even when a route is made publically accessible, only the **content returned** by `page.js` or `route.js` is sent to the client.
+And, even when a route is made publicly accessible, only the **content returned** by `page.js` or `route.js` is sent to the client.
 
 <Image
-  alt="A diagram showing how page.js and route.js files make routes publically accessible."
+  alt="A diagram showing how page.js and route.js files make routes publicly accessible."
   srcLight="/docs/light/project-organization-routable.png"
   srcDark="/docs/dark/project-organization-routable.png"
   width="1600"