chore(i18n,docs): processed translations (#46620)

docs/i18n/chinese-traditional/how-to-work-on-the-docs-theme.md

@@ -1,8 +1,8 @@
 # How to work on documentation
 
-## Work on the docs content
+## Work on the content of the docs
 
-To work on the contributing guidelines, you can edit or add files in the `docs` directory [available here](https://github.com/freeCodeCamp/freeCodeCamp/tree/main/docs). When your changes are merged, it will be made available automatically at the documentation site.
+To work on the contributing guidelines, you can edit or add files in the `docs` directory [available here](https://github.com/freeCodeCamp/freeCodeCamp/tree/main/docs). When your changes are merged, they will be made available automatically at the documentation site.
 
 ### How to create an internal link
 
@@ -25,19 +25,19 @@ When you work on translating docs on Crowdin, make sure to replace the `#target-
 
 ## Work on the docs theme
 
-> [!NOTE] A quick reminder that you do not need to setup anything for working on the content for the documentation site.
+> [!NOTE] A quick reminder that you do not need to set up anything for working on the content for the documentation site.
 > 
 > To work on the contributing guidelines, see [work on the docs content](#work-on-the-docs-content) section.
 
 ### Structure of the docs website
 
-The site is generated using [`docsify`](https://docsify.js.org), and served using GitHub pages.
+The site is generated using [`docsify`](https://docsify.js.org) and served using GitHub pages.
 
 Typically you would not need to change any configuration or build the site locally. In case you are interested, here is how it works:
 
 - The homepage's source for this site is available in [`docs/index.html`](index.html).
 - We serve this file as a SPA using `docsify` and GitHub Pages.
-- The `docsify` script generates the content of `markdown` files in `docs` directory on demand.
+- The `docsify` script generates the content of `markdown` files in the `docs` directory on demand.
 - The homepage is generated from the [`_coverpage.md`](_coverpage.md).
 - the sidebar navigation is generated from [`_sidebar.md`](_sidebar.md).
 

docs/i18n/chinese/how-to-work-on-the-docs-theme.md

@@ -1,8 +1,8 @@
 # How to work on documentation
 
-## Work on the docs content
+## Work on the content of the docs
 
-To work on the contributing guidelines, you can edit or add files in the `docs` directory [available here](https://github.com/freeCodeCamp/freeCodeCamp/tree/main/docs). When your changes are merged, it will be made available automatically at the documentation site.
+To work on the contributing guidelines, you can edit or add files in the `docs` directory [available here](https://github.com/freeCodeCamp/freeCodeCamp/tree/main/docs). When your changes are merged, they will be made available automatically at the documentation site.
 
 ### How to create an internal link
 
@@ -25,19 +25,19 @@ When you work on translating docs on Crowdin, make sure to replace the `#target-
 
 ## Work on the docs theme
 
-> [!NOTE] A quick reminder that you do not need to setup anything for working on the content for the documentation site.
+> [!NOTE] A quick reminder that you do not need to set up anything for working on the content for the documentation site.
 > 
 > To work on the contributing guidelines, see [work on the docs content](#work-on-the-docs-content) section.
 
 ### Structure of the docs website
 
-The site is generated using [`docsify`](https://docsify.js.org), and served using GitHub pages.
+The site is generated using [`docsify`](https://docsify.js.org) and served using GitHub pages.
 
 Typically you would not need to change any configuration or build the site locally. In case you are interested, here is how it works:
 
 - The homepage's source for this site is available in [`docs/index.html`](index.html).
 - We serve this file as a SPA using `docsify` and GitHub Pages.
-- The `docsify` script generates the content of `markdown` files in `docs` directory on demand.
+- The `docsify` script generates the content of `markdown` files in the `docs` directory on demand.
 - The homepage is generated from the [`_coverpage.md`](_coverpage.md).
 - the sidebar navigation is generated from [`_sidebar.md`](_sidebar.md).
 

docs/i18n/espanol/how-to-work-on-the-docs-theme.md

@@ -1,8 +1,8 @@
 # How to work on documentation
 
-## Work on the docs content
+## Work on the content of the docs
 
-To work on the contributing guidelines, you can edit or add files in the `docs` directory [available here](https://github.com/freeCodeCamp/freeCodeCamp/tree/main/docs). When your changes are merged, it will be made available automatically at the documentation site.
+To work on the contributing guidelines, you can edit or add files in the `docs` directory [available here](https://github.com/freeCodeCamp/freeCodeCamp/tree/main/docs). When your changes are merged, they will be made available automatically at the documentation site.
 
 ### How to create an internal link
 
@@ -25,19 +25,19 @@ When you work on translating docs on Crowdin, make sure to replace the `#target-
 
 ## Work on the docs theme
 
-> [!NOTE] Recuerda que no necesitas configurar nada para trabajar en el contenido de la documentación.
+> [!NOTE] A quick reminder that you do not need to set up anything for working on the content for the documentation site.
 > 
 > To work on the contributing guidelines, see [work on the docs content](#work-on-the-docs-content) section.
 
 ### Structure of the docs website
 
-The site is generated using [`docsify`](https://docsify.js.org), and served using GitHub pages.
+The site is generated using [`docsify`](https://docsify.js.org) and served using GitHub pages.
 
 Typically you would not need to change any configuration or build the site locally. In case you are interested, here is how it works:
 
 - El código de la página de inicio para este sitio está disponible en [`docs/index.html`](index.html).
 - Servimos este archivo como SPA utilizando `docsify` y GitHub Pages.
-- El script `docsify` genera el contenido de los archivos`markdown` en el directorio `docs` en demanda.
+- The `docsify` script generates the content of `markdown` files in the `docs` directory on demand.
 - La página de inicio se genera a partir del [`_coverpage.md`](_coverpage.md).
 - La barra de navegación lateral es generada desde [`_sidebar.md`](_sidebar.md).
 

docs/i18n/german/how-to-work-on-the-docs-theme.md

@@ -1,8 +1,8 @@
 # How to work on documentation
 
-## Work on the docs content
+## Work on the content of the docs
 
-To work on the contributing guidelines, you can edit or add files in the `docs` directory [available here](https://github.com/freeCodeCamp/freeCodeCamp/tree/main/docs). When your changes are merged, it will be made available automatically at the documentation site.
+To work on the contributing guidelines, you can edit or add files in the `docs` directory [available here](https://github.com/freeCodeCamp/freeCodeCamp/tree/main/docs). When your changes are merged, they will be made available automatically at the documentation site.
 
 ### How to create an internal link
 
@@ -25,19 +25,19 @@ When you work on translating docs on Crowdin, make sure to replace the `#target-
 
 ## Work on the docs theme
 
-> [!NOTE] Eine kurze Erinnerung daran, dass du für die Arbeit an den Inhalten für die Dokumentationsseite nichts einrichten musst.
+> [!NOTE] A quick reminder that you do not need to set up anything for working on the content for the documentation site.
 > 
 > To work on the contributing guidelines, see [work on the docs content](#work-on-the-docs-content) section.
 
 ### Structure of the docs website
 
-The site is generated using [`docsify`](https://docsify.js.org), and served using GitHub pages.
+The site is generated using [`docsify`](https://docsify.js.org) and served using GitHub pages.
 
 Typically you would not need to change any configuration or build the site locally. In case you are interested, here is how it works:
 
 - Der Quelltext der Homepage ist in [`docs/index.html`](index.html) zu finden.
 - Wir stellen diese Datei als SPA (Single Page Application) mit `docsify` und GitHub Pages bereit.
-- Das `docsify`-Skript generiert bei Bedarf den Inhalt der `markdown`-Dateien im `docs`-Verzeichnis.
+- The `docsify` script generates the content of `markdown` files in the `docs` directory on demand.
 - Die Homepage wird aus der [`_coverpage.md`](_coverpage.md) erstellt.
 - die Navigation in der Seitenleiste wird aus [`_sidebar.md`](_sidebar.md) generiert.
 

docs/i18n/italian/how-to-work-on-the-docs-theme.md

@@ -1,8 +1,8 @@
 # How to work on documentation
 
-## Work on the docs content
+## Work on the content of the docs
 
-To work on the contributing guidelines, you can edit or add files in the `docs` directory [available here](https://github.com/freeCodeCamp/freeCodeCamp/tree/main/docs). When your changes are merged, it will be made available automatically at the documentation site.
+To work on the contributing guidelines, you can edit or add files in the `docs` directory [available here](https://github.com/freeCodeCamp/freeCodeCamp/tree/main/docs). When your changes are merged, they will be made available automatically at the documentation site.
 
 ### How to create an internal link
 
@@ -25,19 +25,19 @@ When you work on translating docs on Crowdin, make sure to replace the `#target-
 
 ## Work on the docs theme
 
-> [!NOTE] Un rapido promemoria per ricordarti che non è necessario configurare nulla per lavorare sul contenuto del sito di documentazione.
+> [!NOTE] A quick reminder that you do not need to set up anything for working on the content for the documentation site.
 > 
 > To work on the contributing guidelines, see [work on the docs content](#work-on-the-docs-content) section.
 
 ### Structure of the docs website
 
-The site is generated using [`docsify`](https://docsify.js.org), and served using GitHub pages.
+The site is generated using [`docsify`](https://docsify.js.org) and served using GitHub pages.
 
 Typically you would not need to change any configuration or build the site locally. In case you are interested, here is how it works:
 
 - Il sorgente della homepage per questo sito è disponibile in [`docs/index.html`](index.html).
 - Serviamo questo file come SPA (Single Page Application) usando `docsify` e GitHub Pages.
-- Lo script `docsify` genera il contenuto del `file markdown` nella directory `docs` su richiesta.
+- The `docsify` script generates the content of `markdown` files in the `docs` directory on demand.
 - La homepage è generata dal file [`_coverpage.md`](_coverpage.md).
 - la navigazione della barra laterale è generata da [`_sidebar.md`](_sidebar.md).
 

docs/i18n/japanese/how-to-work-on-the-docs-theme.md

@@ -1,8 +1,8 @@
 # ドキュメントに貢献する方法
 
-## ドキュメントの内容に貢献する
+## Work on the content of the docs
 
-コントリビューションガイドラインを編集するには、`docs` [ディレクトリ](https://github.com/freeCodeCamp/freeCodeCamp/tree/main/docs) のファイルを編集または追加します。 変更がマージされると、ドキュメントサイトで自動的に公開されます。
+コントリビューションガイドラインを編集するには、`docs` [ディレクトリ](https://github.com/freeCodeCamp/freeCodeCamp/tree/main/docs) のファイルを編集または追加します。 When your changes are merged, they will be made available automatically at the documentation site.
 
 ### 内部リンクを作成する
 
@@ -25,19 +25,19 @@ Crowdin でドキュメントの翻訳を行う際には、`#target-section-head
 
 ## ドキュメントのテーマに貢献する
 
-> [!NOTE] ドキュメントサイトのコンテンツを変更する作業に必要な設定は何もありません。
+> [!NOTE] A quick reminder that you do not need to set up anything for working on the content for the documentation site.
 > 
 > コントリビューションガイドラインを編集するには、[ドキュメントの内容に貢献する](#ドキュメントの内容に貢献する) セクションを参照してください。
 
 ### ドキュメント Web サイトの構造
 
-サイトは [`docsify`](https://docsify.js.org) を使用して生成され、GitHub ページを使用して提供されています。
+The site is generated using [`docsify`](https://docsify.js.org) and served using GitHub pages.
 
 通常、サイトの設定を変更したり、サイトをローカルにビルドしたりする必要はありません。 参考までに、以下のように動作します。
 
 - このサイト向けのホームページのソースは、[`docs/index.html`](index.html) にあります。
 - `docsify` と GitHub Pages を使用して、このファイルを SPA として提供します。
-- `docsify` スクリプトは、`docs` ディレクトリ内の `markdown` ファイルの内容を必要に応じて生成します。
+- The `docsify` script generates the content of `markdown` files in the `docs` directory on demand.
 - ホームページは [`_coverpage.md`](_coverpage.md) から生成されます。
 - サイドバーナビゲーションは [`_sidebar.md`](_sidebar.md) から生成されます。
 

docs/i18n/portuguese/courses-vscode-extension.md

@@ -4,38 +4,38 @@ Aqui detalharemos as diretrizes de manutenção para o [freeCodeCamp/courses-vsc
 
 ## Publicando a extensão
 
-A GitHub Action automagically publishes the extension to the Visual Studio Marketplace, on the release of a new GitHub Release.
+Uma GitHub Action publica automaticamente a extensão no Visual Studio Marketplace, no lançamento de uma nova GitHub Release.
 
-1. Package a new version of the extension:
+1. Pacote de uma nova versão da extensão:
 
 ```bash
 npm run pack -- <tag_type>
 ```
 
-Where `<tag_type>` is one of: `major`, `minor`, `patch`.
+Onde `<tag_type>` é: `major`, `minor` ou `patch`.
 
-2. Push the new version to `main`:
+2. Faça o push da nova versão para `main`:
 
 ```bash
 git commit -am "<tag_type>(<version>): <description>"
 git push
 ```
 
-Optionally, you can push directly to `upstream/main`, but opening a new PR is recommended for a sanity check.
+Como opção, você pode fazer o push diretamente para `upstream/main`, mas abrir um novo PR é recomendado para fins de verificação de sanidade.
 
-3. Create a new GitHub Release using the GitHub UI:
+3. Crie uma GitHub Release usando a UI do GitHub:
 
-- Correctly increment the version number, when creating a new tag.
-- Upload the `.vsix` file with the release.
-- Publish the release, and confirm the action succeeded.
+- Incremente corretamente o número da versão ao criar uma nova tag.
+- Faça o upload do arquivo `.vsix` com a release.
+- Publique a release e confirme que a action foi um sucesso.
 
-> [!NOTE] Creating a release requires write access to the `freeCodeCamp/courses-vscode-extension` repository.
+> [!NOTE] Criar uma release exige acesso de escrita ao repositório `freeCodeCamp/courses-vscode-extension`.
 
 ## Publicando a extensão manualmente
 
-A manual upload to the Visual Studio Marketplace can be achieved, by following these steps:
+Um upload manual para o Visual Studio Marketplace pode ser feito seguindo estes passos:
 
-1. Visit https://marketplace.visualstudio.com/ and sign in
-2. Navigate to the [freeCodeCamp Publisher page](https://marketplace.visualstudio.com/manage/publishers/freecodecamp)
-3. Select the relevant extension, and select `Update`
-4. Upload the file from your local files
+1. Visite https://marketplace.visualstudio.com/ e faça login
+2. Navegue até a [página do editor do freeCodeCamp](https://marketplace.visualstudio.com/manage/publishers/freecodecamp)
+3. Selecione a extensão relevante e selecione `Update`
+4. Faça o upload do arquivo a partir de seus arquivos locais

docs/i18n/portuguese/how-to-work-on-the-docs-theme.md

@@ -1,6 +1,6 @@
 # Como trabalhar na documentação
 
-## Trabalhe no conteúdo da documentação
+## Trabalhar no conteúdo da documentação
 
 Para trabalhar nas diretrizes de contribuição, você pode editar ou adicionar arquivos no diretório `docs` [disponível aqui](https://github.com/freeCodeCamp/freeCodeCamp/tree/main/docs). Ao fazermos o merge de suas alterações, elas são disponibilizadas automaticamente no site da documentação.
 

docs/i18n/ukrainian/how-to-work-on-the-docs-theme.md

@@ -1,8 +1,8 @@
 # How to work on documentation
 
-## Work on the docs content
+## Work on the content of the docs
 
-To work on the contributing guidelines, you can edit or add files in the `docs` directory [available here](https://github.com/freeCodeCamp/freeCodeCamp/tree/main/docs). When your changes are merged, it will be made available automatically at the documentation site.
+To work on the contributing guidelines, you can edit or add files in the `docs` directory [available here](https://github.com/freeCodeCamp/freeCodeCamp/tree/main/docs). When your changes are merged, they will be made available automatically at the documentation site.
 
 ### How to create an internal link
 
@@ -25,19 +25,19 @@ When you work on translating docs on Crowdin, make sure to replace the `#target-
 
 ## Work on the docs theme
 
-> [!NOTE] A quick reminder that you do not need to setup anything for working on the content for the documentation site.
+> [!NOTE] A quick reminder that you do not need to set up anything for working on the content for the documentation site.
 > 
 > To work on the contributing guidelines, see [work on the docs content](#work-on-the-docs-content) section.
 
 ### Structure of the docs website
 
-The site is generated using [`docsify`](https://docsify.js.org), and served using GitHub pages.
+The site is generated using [`docsify`](https://docsify.js.org) and served using GitHub pages.
 
 Typically you would not need to change any configuration or build the site locally. In case you are interested, here is how it works:
 
 - The homepage's source for this site is available in [`docs/index.html`](index.html).
 - We serve this file as a SPA using `docsify` and GitHub Pages.
-- The `docsify` script generates the content of `markdown` files in `docs` directory on demand.
+- The `docsify` script generates the content of `markdown` files in the `docs` directory on demand.
 - The homepage is generated from the [`_coverpage.md`](_coverpage.md).
 - the sidebar navigation is generated from [`_sidebar.md`](_sidebar.md).