Fix Japanese translation for fresh browser per test documentation

[noritaka1166]

Description

Improves the Japanese translation of the “Fresh browser per test” documentation.
This updates wording and formatting for clarity, and translates the remaining English sentence about default browser driver behavior.

Motivation and Context

The page contained an untranslated English sentence and wording that could be improved for natural Japanese readability.

Types of changes

• Change to the site (I have double-checked the Netlify deployment, and my changes look good)
• Code example added (and I also added the example to all translated languages)
• Improved translation
• Added new translation (and I also added a notice to each document missing translation)

Checklist

• I have read the contributing document.
• I have used hugo to render the site/docs locally and I am sure it works.

[netlify]

👷 Deploy request for selenium-dev pending review.

Visit the deploys page to approve it

Name	Link
🔨 Latest commit	59fdc54

[qodo-code-review]

PR Summary by Qodo

Improve Japanese translation for “Fresh browser per test” documentation

📝 Documentation 🕐 Less than 5 minutes

AI Description

• Improve Japanese wording and formatting for readability and consistency.
• Translate the remaining English sentence describing default browser-driver behavior.

High-Level Assessment

The PR’s approach—directly improving the localized markdown copy and translating the remaining English sentence—is the most appropriate and lowest-risk option for a translation-only fix. No alternative technical approach is warranted beyond a quick native-speaker review for nuance/terminology consistency.

Files changed (1) +6 / -6

Documentation (1) +6 / -6

fresh_browser_per_test.ja.mdPolish Japanese bullets and translate browser-driver default behavior sentence +6/-6

Polish Japanese bullets and translate browser-driver default behavior sentence

• Refines the Japanese bullet list for more natural phrasing and better line breaks. Translates the previously untranslated English sentence about GeckoDriver/ChromeDriver starting with a clean user profile by default.

website_and_docs/content/documentation/test_practices/encouraged/fresh_browser_per_test.ja.md

[qodo-code-review]

Code Review by Qodo

🐞 Bugs (0) 📘 Rule violations (0) 📜 Skill insights (0)

1. Intra-sentence hard wraps ✓ Resolved 🐞 Bug ≡ Correctness

Description

fresh_browser_per_test.ja.md introduces intra-sentence newlines after Japanese punctuation (e.g.,
after 「場合は、」 and 「デフォルトで、」); Markdown rendering treats these newlines as whitespace. This can
produce unintended half-width spaces after punctuation in the published page.

Code

website_and_docs/content/documentation/test_practices/encouraged/fresh_browser_per_test.ja.md[R14-17]

+新しい仮想マシンを起動することが現実的でない場合は、
+少なくともテストごとに新しい WebDriver を起動してください。
+GeckoDriver や ChromeDriver など、ほとんどのブラウザドライバーはデフォルトで、
+新しいユーザープロファイルを使用したクリーンで既知の状態で起動します。

Evidence

The modified Japanese page hard-wraps a sentence across lines immediately after 「、」, which will
introduce whitespace between the punctuation and the next character when rendered. Other Japanese
docs keep sentences unbroken on a single line, avoiding this spacing artifact.

website_and_docs/content/documentation/test_practices/encouraged/fresh_browser_per_test.ja.md[12-17]
website_and_docs/content/documentation/webdriver/getting_started/_index.ja.md[17-25]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The Japanese documentation text is hard-wrapped in the middle of sentences (right after 「、」). In Markdown/HTML rendering this newline becomes collapsible whitespace, which can show up as unwanted half-width spaces after Japanese punctuation.

## Issue Context
This was introduced by the translation update and differs from the common style in other Japanese docs, where sentences are typically kept on one source line.

## Fix Focus Areas
- website_and_docs/content/documentation/test_practices/encouraged/fresh_browser_per_test.ja.md[12-17]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

Previous review results

Review updated until commit 59fdc54

Results up to commit 9b19025

🐞 Bugs (0) 📘 Rule violations (0) 📎 Requirement gaps (0) 🎨 UX issues (0) 🔗 Cross-repo conflicts (0) 📜 Skill insights (0)

1. Intra-sentence hard wraps ✓ Resolved 🐞 Bug ≡ Correctness

Description

fresh_browser_per_test.ja.md introduces intra-sentence newlines after Japanese punctuation (e.g.,
after 「場合は、」 and 「デフォルトで、」); Markdown rendering treats these newlines as whitespace. This can
produce unintended half-width spaces after punctuation in the published page.

Code

website_and_docs/content/documentation/test_practices/encouraged/fresh_browser_per_test.ja.md[R14-17]

+新しい仮想マシンを起動することが現実的でない場合は、
+少なくともテストごとに新しい WebDriver を起動してください。
+GeckoDriver や ChromeDriver など、ほとんどのブラウザドライバーはデフォルトで、
+新しいユーザープロファイルを使用したクリーンで既知の状態で起動します。

Evidence

The modified Japanese page hard-wraps a sentence across lines immediately after 「、」, which will
introduce whitespace between the punctuation and the next character when rendered. Other Japanese
docs keep sentences unbroken on a single line, avoiding this spacing artifact.

website_and_docs/content/documentation/test_practices/encouraged/fresh_browser_per_test.ja.md[12-17]
website_and_docs/content/documentation/webdriver/getting_started/_index.ja.md[17-25]

Agent prompt

The issue below was found during a code review. Follow the provided context and guidance below and implement a solution

## Issue description
The Japanese documentation text is hard-wrapped in the middle of sentences (right after 「、」). In Markdown/HTML rendering this newline becomes collapsible whitespace, which can show up as unwanted half-width spaces after Japanese punctuation.

## Issue Context
This was introduced by the translation update and differs from the common style in other Japanese docs, where sentences are typically kept on one source line.

## Fix Focus Areas
- website_and_docs/content/documentation/test_practices/encouraged/fresh_browser_per_test.ja.md[12-17]

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

---

[qodo-code-review]

Code review by qodo was updated up to the latest commit 9b19025

[qodo-code-review]

Code review by qodo was updated up to the latest commit 59fdc54