diff --git a/docs/usage/nextjs.mdx b/docs/usage/nextjs.mdx
index 62d7e6c5a0..d96ad17d1d 100644
--- a/docs/usage/nextjs.mdx
+++ b/docs/usage/nextjs.mdx
@@ -280,7 +280,7 @@ export default function StoreProvider({
 
 If you use Next.js's support for client side SPA-style navigation by using `next/navigation`, then when customers navigate from page to page only the route component will be re-rendered. This means that if you have a Redux store created and provided in the layout component it will be preserved across route changes. This is not a problem if you are only using the store for global, mutable data. However, if you are using the store for per-route data then you will need to reset the route-specific data in the store when the route changes.
 
-Shown below is a `ProductName` example component that uses the Redux store to manage the mutable name of a product. The `ProductName` component part of a product detail route. In order to ensure that we have the correct name in the store we need to set the value in the store any time the `ProductName` component is initially rendered, which happens on any route change to the product detail route.
+Shown below is a `ProductName` example component that uses the Redux store to manage the mutable name of a product. The `ProductName` component is part of a product detail route. In order to ensure that we have the correct name in the store we need to set the value in the store any time the `ProductName` component is initially rendered, which happens on any route change to the product detail route.
 
 ```ts title="app/ProductName.tsx"
 // file: lib/features/product/productSlice.ts noEmit