docs: minor typos and fixes (#73955)

Replaces #73717,
#73719, and
#73788.

docs/01-app/03-building-your-application/01-routing/15-internationalization.mdx

@@ -148,7 +148,7 @@ export default function Root({ children, params }) {
 ## Resources
 
 - [Minimal i18n routing and translations](https://github.com/vercel/next.js/tree/canary/examples/i18n-routing)
-- [`next-intl`](https://next-intl-docs.vercel.app/docs/next-13)
+- [`next-intl`](https://next-intl.dev)
 - [`next-international`](https://github.com/QuiiBz/next-international)
 - [`next-i18n-router`](https://github.com/i18nexus/next-i18n-router)
 - [`paraglide-next`](https://inlang.com/m/osslbuzt/paraglide-next-i18n)

docs/01-app/03-building-your-application/09-authentication/index.mdx

@@ -522,7 +522,7 @@ There are two types of sessions:
 1. [**Stateless**](#stateless-sessions): Session data (or a token) is stored in the browser's cookies. The cookie is sent with each request, allowing the session to be verified on the server. This method is simpler, but can be less secure if not implemented correctly.
 2. [**Database**](#database-sessions): Session data is stored in a database, with the user's browser only receiving the encrypted session ID. This method is more secure, but can be complex and use more server resources.
 
-> **Good to know:** While you can use either method, or both, we recommend using session management library such as [iron-session](https://github.com/vvo/iron-session) or [Jose](https://github.com/panva/jose).
+> **Good to know:** While you can use either method, or both, we recommend using a session management library such as [iron-session](https://github.com/vvo/iron-session) or [Jose](https://github.com/panva/jose).
 
 ### Stateless Sessions
 

docs/01-app/03-building-your-application/11-upgrading/03-version-15.mdx

@@ -577,7 +577,7 @@ To continue using Speed Insights, follow the [Vercel Speed Insights Quickstart](
 
 The `geo` and `ip` properties on `NextRequest` have been removed as these values are provided by your hosting provider. A [codemod](/docs/app/building-your-application/upgrading/codemods#150) is available to automate this migration.
 
-If you are using Vercel, you can alternatively use the `geolocation` and `ipAddress` functions from [`@vercel/functions](https://vercel.com/docs/functions/vercel-functions-package) instead:
+If you are using Vercel, you can alternatively use the `geolocation` and `ipAddress` functions from [`@vercel/functions`](https://vercel.com/docs/functions/vercel-functions-package) instead:
 
 ```ts filename="middleware.ts"
 import { geolocation } from '@vercel/functions'