The Japanese translation is broken

### Describe the bug

The quality of the Japanese translation seems to be entirely machine-generated, and I cannot overlook the issues on the following page. It appears that placeholders like **{0}** and **{1}** should have variables inserted, but instead, it shows **0}** without substitution. This makes it unsuitable for enterprise use.

http://localhost:3000/
> **0}** で何ができるか、これらのサンプルX線を試してみてください。
> Try out these sample x-rays to see what **Metabase** can do.

http://localhost:3000/getting-started
> **0}** を設定する。
> Set up your **Metabase**

>**0}** を最大限に活用する
>Get the most out of **Metabase**

>Metabaseは多くのことができます。**1}** 、データ可視化、モデリング、その他のデータトピックについてもっと学ぶには、以下をご覧ください。
>Metabase can do a lot. To learn more—about **Metabase** , data visualization, modeling, and other data topics—check out our sites.

http://localhost:3000/admin/performance/databases
> **0}** で各データベース、ダッシュボード、クエリの詳細なキャッシュ制御を取得する
> Get granular caching controls for each database, dashboard, and query with **Metabase Pro**.

Additionally, there are many sentences with issues related to inverted word order, such as phrases like "Product Summary of." Since Japanese word order is different from English, the position of the placeholder needs to be changed, otherwise the display will be extremely unnatural.

I followed the manual and went to POEditor, but I received the error message: "This project can't accept new contributors at this time. Please try again later." It seems that I cannot edit it. Does this mean I should edit it on GitHub?

```JSON
{
"browser-info": {
"language": "ja",
"platform": "MacIntel",
"userAgent": "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/131.0.0.0 Safari/537.36",
"vendor": "Google Inc."
},
"metabase-info": {
"databases": [
"h2"
],
"run-mode": "prod",
"plan-alias": "",
"version": {
"date": "2025-01-07",
"tag": "v0.52.5",
"hash": "cc77eeb"
},
"settings": {
"report-timezone": null
},
"hosting-env": "unknown",
"application-database": "h2",
"application-database-details": {
"database": {
"name": "H2",
"version": "2.1.214 (2022-06-13)"
},
"jdbc-driver": {
"name": "H2 JDBC Driver",
"version": "2.1.214 (2022-06-13)"
}
}
},
"system-info": {
"file.encoding": "UTF-8",
"java.runtime.name": "OpenJDK Runtime Environment",
"java.runtime.version": "21.0.5+11-LTS",
"java.vendor": "Eclipse Adoptium",
"java.vendor.url": "https://adoptium.net/",
"java.version": "21.0.5",
"java.vm.name": "OpenJDK 64-Bit Server VM",
"java.vm.version": "21.0.5+11-LTS",
"os.name": "Linux",
"os.version": "5.10.124-linuxkit",
"user.language": "en",
"user.timezone": "GMT"
}
}
```

### Severity

Just by looking at the localhost:3000, Japanese companies will likely decide not to adopt the product.

### Additional context

_No response_

Start by reviewing the Japanese strings reported on the localhost:3000, /getting-started, and /admin/performance/databases pages, then check the documented POEditor workflow and its contributor restriction. Confirm where these translations are maintained before changing them; done means placeholders render with their intended names and the Japanese wording is corrected on the cited pages.

Written by the indexing model from the issue text.