chore(i8n,docs): processed translations (#41252)

Co-authored-by: Crowdin Bot <support+bot@crowdin.com>

docs/i18n/portuguese/how-to-work-on-coding-challenges.md

@@ -49,7 +49,7 @@ Challenge description text, in markdown
 <div>
   example code
 </div>
-```
+````
 
 # --instructions--
 
@@ -184,7 +184,7 @@ MongoDB server version: 3.4.10
 ...
 $ ObjectId()
 ObjectId("5a474d78df58bafeb3535d34")
-```
+````
 
 The result is a new id, for example `5a474d78df58bafeb3535d34` above.
 
@@ -202,7 +202,7 @@ Naming things is hard. We've made it easier by imposing some constraints.
 
 All challenge titles should be explicit and should follow this pattern:
 
-[verb][object clause]
+\[verb\]\[object clause\]
 
 Here are some example challenge names:
 
@@ -255,14 +255,14 @@ Our goal is to have thousands of 2-minute challenges. These can flow together an
 
 Here are specific formatting guidelines for challenge text and examples:
 
-- Language keywords go in `\`` backticks. For example, HTML tag names or CSS property names.
-- References to code parts (i.e. function, method, or variable names) should be wrapped in `\`` backticks. See example below:
+- Language keywords go in `` \` `` backticks. For example, HTML tag names or CSS property names.
+- References to code parts (i.e. function, method, or variable names) should be wrapped in `` \` `` backticks. See example below:
 ```md
 Use `parseInt` to convert the variable `realNumber` into an integer.
 ```
-- References to file names and path directories (e.g. `package.json`, `src/components`) should be wrapped in `\`` backticks.
+- References to file names and path directories (e.g. `package.json`, `src/components`) should be wrapped in `` \` `` backticks.
 - Multi-line code blocks **must be preceded by an empty line**. The next line must start with three backticks followed immediately by one of the [supported languages](https://prismjs.com/#supported-languages). To complete the code block, you must start a new line which only has three backticks and **another empty line**. See example below:
-- Whitespace matters in Markdown, so we recommend that you make it visible in your editor. 
+- Whitespace matters in Markdown, so we recommend that you make it visible in your editor.
 
 **Note:** If you are going to use an example code in YAML, use `yaml` instead of `yml` for the language to the right of the backticks.
 
@@ -272,7 +272,7 @@ The following is an example of code:
 
 [YOUR CODE HERE]
 
-```
+````
 ````
 
 - Additional information in the form of a note should be surrounded by blank lines, and formatted: `**Note:** Rest of note text...`
@@ -307,7 +307,7 @@ Example of valid single line JavaScript comment:
 
 ```js
 // Only change code below this line
-```
+````
 
 Example of a valid CSS comment:
 
@@ -363,14 +363,13 @@ class MyComponent extends React.Component {
 
 There are separate comment dictionaries for each language. The [English version of the comment dictionary](/curriculum/dictionaries/english/comments.js) is the basis for the translations found in the corresponding non-English versions of the files. The non-English version of the Chinese comment dictionary would be located at `/curriculum/dictionaries/chinese/comments.js`.  Each dictionary consists of an array of objects with a unique `id` property and a `text` property.  Only the `text` should be modified to encompass the translation of the corresponding English comment.
 
-Some comments may contain a word/phrase that should not be translated. For example, variable names or proper library names like "React" should not be translated.  See the comment below as an example. The word `myGlobal` should not be translated. 
+Some comments may contain a word/phrase that should not be translated. For example, variable names or proper library names like "React" should not be translated.  See the comment below as an example. The word `myGlobal` should not be translated.
 
 ```text
 Declare the myGlobal variable below this line
 ```
-
->[!NOTE]
->
+> [!NOTE]
+> 
 > We are working on an integration to make it possible to work on i18n for the comment dictionary.
 
 ## Hints and Solutions
@@ -384,7 +383,7 @@ If you find a problem with an existing challenge's hints/solutions topic, you ca
 Take the following steps when adding a new challenge hints/solutions related topic.
 
 1. Start by following the same steps for creating a new topic but review the next for creating the title.
-2. The title of the topic should start with `freeCodeCamp Challenge Guide: ` concatenated with the actual title of the curriculum challenge. For example, if the challenge is named "`Chunky Monkey`", the topic title would be "`freeCodeCamp Challenge Guide: Chunky Monkey`".
+2. The title of the topic should start with `freeCodeCamp Challenge Guide:` concatenated with the actual title of the curriculum challenge. For example, if the challenge is named "`Chunky Monkey`", the topic title would be "`freeCodeCamp Challenge Guide: Chunky Monkey`".
 3. `camperbot` should be the owner of these topics/posts, so you will need to request an admin to change the ownership of the main post to `camperbot`.
 4. Once the new topic is created, a forum topic id is created. It is located at the end of the forum topic URL. This id must be added to the frontmatter of the curriculum challenge file via the normal pull request process for the `Get a Hint` button to link to the topic.
 
@@ -428,7 +427,7 @@ Hint goes here
 function myFunc() {
   console.log('Hello World!');
 }
-```
+````
 
 #### Code Explanation
 
@@ -449,7 +448,7 @@ Before you [create a pull request](how-to-open-a-pull-request.md) for your chang
 
 1. To test all challenges run the below command from the root directory
 
-```
+````
 npm run test:curriculum
 ``` 
 
@@ -474,13 +473,11 @@ You are also able to test one challenge individually by performing the following
 2. Run the following for each challenge file for which you have changed (replacing `challenge-title-goes-here` with the full title of the challenge):
 
    ```
-   npm run test -- -g challenge-title-goes-here
-   ```
+   npm run test -- -g challenge-title-goes-here ```
 
 Once you have verified that each challenge you've worked on passes the tests, [please create a pull request](https://github.com/freeCodeCamp/freeCodeCamp/blob/main/docs/how-to-open-a-pull-request.md).
 
-> [!TIP]
-> You can set the environment variable `LOCALE` in the `.env` to the language of the challenge(s) you need to test.
+> [!TIP] You can set the environment variable `LOCALE` in the `.env` to the language of the challenge(s) you need to test.
 > 
 > The currently accepted values are `english` and `chinese`, with `english` being set by default.