diff --git a/docs/02-app/01-building-your-application/01-routing/10-parallel-routes.mdx b/docs/02-app/01-building-your-application/01-routing/10-parallel-routes.mdx
index 0bffa7457777f..ed6e96da454b4 100644
--- a/docs/02-app/01-building-your-application/01-routing/10-parallel-routes.mdx
+++ b/docs/02-app/01-building-your-application/01-routing/10-parallel-routes.mdx
@@ -167,7 +167,7 @@ export default function Layout({ user, admin }) {
 }
 ```
 
-## Tab Groups
+### Tab Groups
 
 You can add a `layout` inside a slot to allow users to navigate the slot independently. This is useful for creating tabs.
 
@@ -307,7 +307,7 @@ export default function Page() {
 > - The convention used to intercept the route, e.g. `(.)`, depends on your file-system structure. See [Intercepting Routes convention](/docs/app/building-your-application/routing/intercepting-routes#convention).
 > - By separating the `<Modal>` functionality from the modal content (`<Login>`), you can ensure any content inside the modal, e.g. [forms](/docs/app/building-your-application/data-fetching/server-actions-and-mutations#forms), are Server Components. See [Interleaving Client and Server Components](/docs/app/building-your-application/rendering/composition-patterns#supported-pattern-passing-server-components-to-client-components-as-props) for more information.
 
-### Opening the modal
+#### Opening the modal
 
 Now, you can leverage the Next.js router to open and close the modal. This ensures the URL is correctly updated when the modal is open, and when navigating backwards and forwards.
 
@@ -353,7 +353,7 @@ export default function Layout({ auth, children }) {
 
 When the user clicks the `<Link>`, the modal will open instead of navigating to the `/login` page. However, on refresh or initial load, navigating to `/login` will take the user to the main login page.
 
-### Closing the modal
+#### Closing the modal
 
 You can close the modal by calling `router.back()` or by using the `Link` component.
 
diff --git a/docs/02-app/01-building-your-application/01-routing/11-intercepting-routes.mdx b/docs/02-app/01-building-your-application/01-routing/11-intercepting-routes.mdx
index 180e970c828be..c9cf7ee2af75d 100644
--- a/docs/02-app/01-building-your-application/01-routing/11-intercepting-routes.mdx
+++ b/docs/02-app/01-building-your-application/01-routing/11-intercepting-routes.mdx
@@ -74,7 +74,7 @@ Consider the following UI pattern, where a user can open a photo modal from a ga
   height="976"
 />
 
-In the above example, the path to the `photo` segment can use the `(..)` matcher since `@modal` is a _slot_ and not a _segment_. This means that the `photo` route is only one _segment_ level higher, despite being two _file-system_ levels higher.
+In the above example, the path to the `photo` segment can use the `(..)` matcher since `@modal` is a slot and **not** a segment. This means that the `photo` route is only one segment level higher, despite being two file-system levels higher.
 
 See the [Parallel Routes](/docs/app/building-your-application/routing/parallel-routes#modals) documentation for a step-by-step example, or see our [image gallery example](https://github.com/vercel-labs/nextgram).