From 732a64dda9d33324ea54f059eab71a0814a58e99 Mon Sep 17 00:00:00 2001
From: Loris Sigrist <43482866+LorisSigrist@users.noreply.github.com>
Date: Mon, 3 Jun 2024 20:43:31 +0200
Subject: [PATCH] chore(docs): Update Inlang Link on Internationalization Page
 (#66488)
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

Hi 👋 Inlang dev here

This PR switches the Link to Inlang's i18n solution in the
Internationalization docs to point directly to
[Paraglide-Next](https://inlang.com/m/osslbuzt/paraglide-next-i18n)
since that's the most relevant page for NextJS developers looking for an
i18n library.

<!-- Thanks for opening a PR! Your contribution is much appreciated.
To make sure your PR is handled as smoothly as possible we request that
you follow the checklist sections below.
Choose the right checklist for the change(s) that you're making:

## For Contributors

### Improving Documentation

- Run `pnpm prettier-fix` to fix formatting issues before opening the
PR.
- Read the Docs Contribution Guide to ensure your contribution follows
the docs guidelines:
https://nextjs.org/docs/community/contribution-guide

### Adding or Updating Examples

- The "examples guidelines" are followed from our contributing doc
https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md
- Make sure the linting passes by running `pnpm build && pnpm lint`. See
https://github.com/vercel/next.js/blob/canary/contributing/repository/linting.md

### Fixing a bug

- Related issues linked using `fixes #number`
- Tests added. See:
https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md

### Adding a feature

- Implements an existing feature request or RFC. Make sure the feature
request has been accepted for implementation before opening a PR. (A
discussion must be opened, see
https://github.com/vercel/next.js/discussions/new?category=ideas)
- Related issues/discussions are linked using `fixes #number`
- e2e tests added
(https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs)
- Documentation added
- Telemetry added. In case of a feature if it's used or not.
- Errors have a helpful link attached, see
https://github.com/vercel/next.js/blob/canary/contributing.md


## For Maintainers

- Minimal description (aim for explaining to someone not on the team to
understand the PR)
- When linking to a Slack thread, you might want to share details of the
conclusion
- Link both the Linear (Fixes NEXT-xxx) and the GitHub issues
- Add review comments if necessary to explain to the reviewer the logic
behind a change

### What?

### Why?

### How?

Closes NEXT-
Fixes #

-->

Co-authored-by: Sam Ko <sam@vercel.com>
---
 .../01-routing/15-internationalization.mdx                      | 2 +-
 .../01-routing/10-internationalization.mdx                      | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/02-app/01-building-your-application/01-routing/15-internationalization.mdx b/docs/02-app/01-building-your-application/01-routing/15-internationalization.mdx
index 1fb2442df42be..5fc73676e1a27 100644
--- a/docs/02-app/01-building-your-application/01-routing/15-internationalization.mdx
+++ b/docs/02-app/01-building-your-application/01-routing/15-internationalization.mdx
@@ -151,4 +151,4 @@ export default function Root({ children, params }) {
 - [`next-intl`](https://next-intl-docs.vercel.app/docs/next-13)
 - [`next-international`](https://github.com/QuiiBz/next-international)
 - [`next-i18n-router`](https://github.com/i18nexus/next-i18n-router)
-- [`inlang`](https://inlang.com/c/nextjs)
+- [`paraglide-next`](https://inlang.com/m/osslbuzt/paraglide-next-i18n)
diff --git a/docs/03-pages/01-building-your-application/01-routing/10-internationalization.mdx b/docs/03-pages/01-building-your-application/01-routing/10-internationalization.mdx
index 58f65f92bc76b..b3b8cfeefe136 100644
--- a/docs/03-pages/01-building-your-application/01-routing/10-internationalization.mdx
+++ b/docs/03-pages/01-building-your-application/01-routing/10-internationalization.mdx
@@ -13,7 +13,7 @@ description: Next.js has built-in support for internationalized routing and lang
 
 Next.js has built-in support for internationalized ([i18n](https://en.wikipedia.org/wiki/Internationalization_and_localization#Naming)) routing since `v10.0.0`. You can provide a list of locales, the default locale, and domain-specific locales and Next.js will automatically handle the routing.
 
-The i18n routing support is currently meant to complement existing i18n library solutions like [`react-intl`](https://formatjs.io/docs/getting-started/installation), [`react-i18next`](https://react.i18next.com/), [`lingui`](https://lingui.dev/), [`rosetta`](https://github.com/lukeed/rosetta), [`next-intl`](https://github.com/amannn/next-intl), [`next-translate`](https://github.com/aralroca/next-translate), [`next-multilingual`](https://github.com/Avansai/next-multilingual), [`tolgee`](https://tolgee.io/integrations/next), [`inlang`](https://inlang.com/c/nextjs) and others by streamlining the routes and locale parsing.
+The i18n routing support is currently meant to complement existing i18n library solutions like [`react-intl`](https://formatjs.io/docs/getting-started/installation), [`react-i18next`](https://react.i18next.com/), [`lingui`](https://lingui.dev/), [`rosetta`](https://github.com/lukeed/rosetta), [`next-intl`](https://github.com/amannn/next-intl), [`next-translate`](https://github.com/aralroca/next-translate), [`next-multilingual`](https://github.com/Avansai/next-multilingual), [`tolgee`](https://tolgee.io/integrations/next), [`paraglide-next`](https://inlang.com/m/osslbuzt/paraglide-next-i18n) and others by streamlining the routes and locale parsing.
 
 ## Getting started