docs: Improve wording

Author: amannn

docs/src/pages/docs/routing.mdx

@@ -107,7 +107,7 @@ In this case, requests for all locales will be rewritten to have the locale only
 2. [Alternate links](#alternate-links) are disabled in this mode since URLs might not be unique per locale. Due to this, consider including these yourself, or set up a [sitemap](/docs/environments/actions-metadata-route-handlers#sitemap) that links localized pages via `alternates`.
 3. You can consider increasing the [`maxAge`](#locale-cookie) attribute of the locale cookie to a longer duration to remember the user's preference across sessions.
 
-#### Custom prefixes [#locale-prefix-custom]
+#### `prefixes` [#locale-prefix-prefixes]
 
 If you'd like to customize the user-facing prefix, you can provide a locale-based mapping:
 
@@ -160,7 +160,9 @@ If you'd like to encode custom information in the locale, you can use arbitrary
 
 ### `pathnames` [#pathnames]
 
-Many apps choose to localize pathnames, especially when search engine optimization is relevant, e.g.:
+Many apps choose to localize pathnames, especially when search engine optimization is relevant.
+
+**Example:**
 
 - `/en/about`
 - `/de/ueber-uns`
@@ -251,7 +253,7 @@ revalidatePath('/de/news/some-article');
 revalidatePath('/de/neuigkeiten/some-article');
 ```
 
-When in doubt, you can revalidate both paths to be on the safe side.
+When in doubt, you can revalidate with `revalidateTag` instead.
 
 See also: [`vercel/next.js#59825`](https://github.com/vercel/next.js/issues/59825)
 
@@ -323,7 +325,7 @@ If you want to serve your localized content based on different domains, you can
 - `ca.example.com/fr`: `fr-CA`
 - `fr.example.com`: `fr-FR`
 
-In many cases, `domains` are combined with a [`localePrefix`](#locale-prefix) setting to achieve results as shown above. Also [custom prefixes](#locale-prefix-custom) can be used to customize the user-facing prefix per locale.
+In many cases, `domains` are combined with a [`localePrefix`](#locale-prefix) setting to achieve results as shown above. Also [custom prefixes](#locale-prefix-prefixes) can be used to customize the user-facing prefix per locale.
 
 ```tsx filename="routing.ts"
 import {defineRouting} from 'next-intl/routing';