Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Change "publically" to "publicly" in the routing docs #52966

Merged
merged 2 commits into from
Jul 20, 2023
Merged

Change "publically" to "publicly" in the routing docs #52966

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
96c34d7
Change "publically" to "publicly" in the routing docs
cassidoo Jul 20, 2023
690340e
Change "publically" to "publicly" in the colocation docs
cassidoo Jul 20, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
8 changes: 4 additions & 4 deletions docs/02-app/01-building-your-application/01-routing/12-colocation.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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"
Expand Down
2 changes: 1 addition & 1 deletion docs/02-app/01-building-your-application/01-routing/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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"
Expand Down