docs: fix dead inlang translation links (moved to Fink)

[1t1sCooL]

The inlang translation links in the README are dead — inlang moved its online editor to the Fink app and retired the old badge endpoint:

• https://inlang.com/editor/github.com/AppFlowy-IO/AppFlowy (and its ?ref=badge variant) → 404 → https://fink.inlang.com/github.com/AppFlowy-IO/AppFlowy (HTTP 200, loads the AppFlowy project).
• The badge image https://inlang.com/badge?url=... → 404 with no working successor endpoint (badge.inlang.com 403s even via camo), so the broken badge image was replaced with a plain "Translate on Fink" link.

Summary by Sourcery

Update README translation links to use Fink’s working AppFlowy editor.

Bug Fixes:

• Replace dead inlang translation links in the README with working Fink links.

Documentation:

• Update the translations section to direct contributors to the Fink online editor and provide a plain translation link instead of the retired badge.

[CLAassistant]

All committers have signed the CLA.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the README translation links from the retired inlang editor and badge endpoint to Fink, replacing the broken badge image with a working plain text link.

File-Level Changes

Change	Details	Files
Replace retired inlang translation URLs and badge markup with the current Fink destination.	Update the README’s primary translation link to Fink. Replace the broken image badge with a plain text link because no working badge endpoint is available. Update the translation instructions to point the online editor reference at Fink.	README.md

Possibly linked issues

• #[Bug] docs: Broken Inlang translation link in README (404 Error): The PR directly fixes the reported 404 links by replacing retired Inlang URLs with the working Fink editor.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've found 1 issue

Prompt for AI Agents

Please address the comments from this code review:

## Individual Comments

### Comment 1
<location path="README.md" line_range="99" />
<code_context>

 To add translations, you can manually edit the JSON translation files in `/frontend/resources/translations`, use
-the [inlang online editor](https://inlang.com/editor/github.com/AppFlowy-IO/AppFlowy), or
+the [inlang online editor](https://fink.inlang.com/github.com/AppFlowy-IO/AppFlowy), or
 run `npx inlang machine translate` to add missing translations.

</code_context>
<issue_to_address>
**nitpick:** The README still labels the destination as the “inlang online editor,” but the link now opens Fink, so the documentation identifies the service incorrectly and can confuse contributors looking for the editor.

**Suggested fix:** Rename the link text to “Fink online editor” or “Fink editor.”

```suggestion
the [Fink online editor](https://fink.inlang.com/github.com/AppFlowy-IO/AppFlowy), or
```
</issue_to_address>

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}