jiebi/CodeConvo huggingface dataset:
Change:
In the document, there is a sentence saying this: But this section is talking about dealing with solutions , it should be changed to this: here is the file If you would like to fix this issue, please make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our moderators will guide you through this.
Hi there! I'm definitely a first-timer and would like to fix this. You can assign this issue to me.
Hi feel free to open a pull request after you have read our contribution guide
Hey there! I would like to fix this issue,you can assign this to me.
Hey feel free to open a pull request after you have read our contribution guide

Discussion:
If the OP (Original Poster) replies within a freeCodeCamp curriculum help thread with their final solution, blur it and use the **Blurred Spoiler Solution** canned reply. <del> If a user creates a thread asking for feedback on a solution, move the thread to the feedback subforum and blur the solution, as necessary. If the user is only posting the solution to show if off, then unlist the thread and use the **Solutions Thread** canned reply. </del> <ins> If a user creates a thread asking for feedback on a solution, move the thread to the feedback subforum and blur the solution, as necessary. If the user is only posting the solution to show it off, then unlist the thread and use the **Solutions Thread** canned reply. </ins> ### Underage Users
Change:
There is an extra quote in the string below it can be removed as it isn't required Here is the file: If you would like to fix this issue, please make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our moderators will guide you through this.
Can I work on this issue?
Yea, feel free to open PR, after you have read our contribution guideline
I have created the pull request, please review it.
Can i also contribute to this issue?
Yes, there is no pull request that follows the contribution guideline. If you open PR that follows it, that pr will be merged and closes the issue with it
Thank you

Discussion:
}; ``` <del> You can send a <b>DELETE</b> request to `/api/books` to delete all books in the database. The returned response will be the string `'complete delete successful` if successful. </del> <ins> You can send a <b>DELETE</b> request to `/api/books` to delete all books in the database. The returned response will be the string `complete delete successful` if successful. </ins> ```js async (getUserInput) => {
Change:
I noticed that the doc describing the process for updating the docs (how-to-work-on-the-docs-) doesn't explicitly say that when adding a brand new doc file, the file should be updated (or evaluated to see if the new file should be listed there). I'm not sure if 100% of new doc files should in fact get to the , but I feel it should be mentioned as a possible area that needs to be looked at when a person is adding a brand new doc file. (ps. About a month ago I created a new doc file for onboarding of mods and the PR was accepted and merged, but no change was made to the because I was unaware of it till just now... I now need to go back to modify this file to 'publish' the new doc) how-to-work-on-the-docs- N/A Update the how-to-work-on-the-docs- to call out the need to evaluate updating the specifically when creating a brand new doc file. No response

Discussion:
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. <ins> When adding a new file to the `docs` directory, you should evaluate if the file should also be added to the sidebar navigation. We typically create a link in the [`_sidebar.md`](_sidebar.md) file for new and independent guides. Alternatively, You may follow the instructions below on creating an internal link for supporting guides. </ins> ### How to create an internal link If you want to create a link targeting a different section of the contributing guidelines, follow this format:

- We serve this file as a SPA using `docsify` and GitHub Pages. - 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). <del> - the sidebar navigation is generated from [`_sidebar.md`](_sidebar.md). </del> <ins> - The sidebar navigation is generated from [`_sidebar.md`](_sidebar.md). </ins> ### Serving the documentation site locally
Change:
In : Step 43 Increase the psuedo-element's transparency by 30%. psuedo instead of pseudo just loading the page change for : Increase the pseudo-element's transparency by 30%. !
Thanks for opening this issue. This looks something that can be fixed by "first time" code contributors to this repository. Here are the files that you should be looking at to work on a fix: List of files: Please make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our moderators will guide you through this. Sometimes we may get more than one pull requests. We typically accept the most quality contribution followed by the one that is made first. Happy contributing.
Hey We typically do not assign issues. Instead, we accept the first pull request that comprehensively solves the issue. Please make sure you read . We prioritize contributors following the instructions in our guide. Join us in or if you need help contributing - our community will be happy to assist you.
currently following the guideline to make my PR

Discussion:
# --description-- <del> Increase the psuedo-element's transparency by `30%`. </del> <ins> Increase the pseudo-element's transparency by `30%`. </ins> # --hints--
Change:
In step , currently, the instruction says: The at the beginning of the other commands at the bottom stands for "meta". It's a key that doesn't exist on most keyboards. If you're on OSX it means press then then the letter. If you are on another system, press then the letter. Use the exit command to get back to the terminal. Instead of this, the instruction should be as follows: The at the beginning of the other commands at the bottom stands for "meta". It's a key that doesn't exist on most keyboards. If you're on OSX it means press then the letter. If you are on another system, press then the letter. Use the exit command to get back to the terminal. NOTE: There's an extra then in the third sentence i.e. If you're on OSX it means press then the letter. In step , currently, the instruction says: That construction team must be working hard Open the file again to continue building. Instead of this, the instruction should be as follows: That construction team must be working hard . Open the file again to continue building. NOTE: There's a missing full stop ( ) after within the first sentence. In step , the instruction should be as follows: The at the beginning of the other commands at the bottom stands for "meta". It's a key that doesn't exist on most keyboards. If you're on OSX it means press then the letter. If you are on another system, press then the letter. Use the exit command to get back to the terminal. In step , the instruction should be as follows: That construction team must be working hard . Open the file again to continue building. <img width="707" alt="image" src="https://user-"<img width="706" alt="image" src="https://user-"- Device: Laptop OS: macOS 13.0.1 Browser: Chrome Version: 107.0.5304.110

Discussion:
h4.negative-10.text-nowrap Community Builder img.profile-image(src='https://s3.amazonaws.com/freecodecamp/branden-byers.jpg' alt="Branden Byers picture") h4.text-nowrap Madison, Wisconsin <del> p.negative-10 "I'm a massage therapist and Stay-at-home-dad. I learned Hypercard, then Rails, but now I feel at home with JavaScript." </del> <ins> p.negative-10 "Cookbook author and stay-at-home-dad. Started coding as a kid, got distracted, but now I'm back in full JavaScript force!" </ins> .col-xs-12.col-sm-4.col-md-3.team-member h3.negative-10.text-nowrap Michael Johnson h4.negative-10.text-nowrap Nonprofit Coordinator

h4.negative-10.text-nowrap Live Content Manager img.profile-image(src='https://s3.amazonaws.com/freecodecamp/jason-rueckert.jpg' alt="Jason Rueckert's picture") h4.text-nowrap Seattle, Washington <del> p.negative-10 "My high school job was testing basketball shoes for Nike. I learned code to work smarter, not harder. I have no thyroid." </del>  No newline at end of file <ins> p.negative-10 "My high school job was testing basketball shoes for Nike. I learned code to work smarter, not harder. I have no thyroid." </ins>
Change:
Been puzzling over why so many people see the instructions in step 4 of the cat photo app and ignore the requested location of "above the p element" when adding their new comment line of code. Discussed with and he noticed that the editor doesn't show an empty line where it expects the code to go (usually it does on other steps). This issue then is to request a blank line be to the editor for step 4 above the p element line to show where the expected new line of code should be written. Editor should display a single blank line above the p element. No response not applicable Example of forum post where learner just doesn't understand how the code can be -above- discussion in the contributors area of the discord channel (start point here )
I don't have an option for this. However, I do think that we should take away the empty space that is created below the tag as there is no reason why it needs to be there, and might lead to confusion.
Hi and I want to work on this issue. Could you assign it to me?
Issues don't get assigned so just create a new branch and get to work! Make sure you have read the rules for contributing:
Whoops, I have missed a step If you would like to fix this issue, please make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our moderators will guide you through this.

Discussion:
<h1>CatPhotoApp</h1> <h2>Cat Photos</h2> --fcc-editable-region-- <p>Click here to view more cat photos.</p> --fcc-editable-region--
Change:
Describe the bug there are situations in which you need to add special character (like ) which is fine, but for RTL the direction is reverted so the placement of the special character is reverted, as well. Here is the file Likely we have the CSS property to fix this, we simply need the element to wrap that word so we can apply them. To fix this issue wrap the , between markdown code, like this , so the sentence will be something like this If you would like to fix this issue, please make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our moderators will guide you through this.
There is a second mentioning of .exe in this sentence if it changed to too, that would be awesome
Hi, Has this issue been assigned to someone? If not, could you please assign this to me?
We don't assign issues, feel free to open PR after reading our docs

Discussion:
<details><summary>Installing MailHog on Windows</summary> <del> Download the latest version of MailHog from [MailHog's official repository](https://github.com/mailhog/MailHog/releases). Locate and click on the link for your Windows version (32 or 64 bit) and a .exe file will be downloaded to your computer. </del> <ins> Download the latest version of MailHog from [MailHog's official repository](https://github.com/mailhog/MailHog/releases). Locate and click on the link for your Windows version (32 or 64 bit) and a `.exe` file will be downloaded to your computer. </ins> When the download completes, click to open the file. A Windows firewall notification may appear, requesting access permission for MailHog. A standard Windows command line prompt will open where MailHog will be running once firewall access is granted. <del> Close MailHog by closing the command prompt window. To start MailHog again, click on the MailHog executable (.exe) file that was downloaded initially - it is not necessary to download a new MailHog installation file. </del> <ins> Close MailHog by closing the command prompt window. To start MailHog again, click on the MailHog executable (`.exe`) file that was downloaded initially - it is not necessary to download a new MailHog installation file. </ins> Start [using MailHog](#using-mailhog).
Change:
The catphotoapp project’s step 16 asks users to use a section element however if a user type Section as the tag name, the test rejects the code even though html tags are supposed to be case insensitive. It is expected that this code passes since the correct section element is being created. No response Not applicable Issue found on the forum

Discussion:
Your `section` element should have a closing tag. Closing tags have a `/` just after the `<` character. ```js <del> assert(code.match(/</section>/)); </del> <ins> assert(code.match(/</sections*>/i)); </ins> ``` The entire `section` element should be between the opening and closing tags of the `main` element.

<html> <body> --fcc-editable-region-- <main> <h1>CatPhotoApp</h1> <h2>Cat Photos</h2> <!-- TODO: Add link to cat photos --> <p>Click here to view more <a target="_blank" href="https://freecatphotoapp.com">cat photos</a>.</p> <a href="https://freecatphotoapp.com"><img src="https://cdn.freecodecamp.org/curriculum/cat-photo-app/relaxing-cat.jpg" alt="A cute orange cat lying on its back."></a> </main> --fcc-editable-region-- </body> </html>
Change:
Describe the bug A clear and concise description of what the bug is. In this string, we are missing code tags around the word . We can change it to this string Here is the file If you would like to fix this issue, please make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our moderators will guide you through this.
Hey, I can do it
Hey ! Could you please assign it to me. I would be glad to start contributing in open-source with freeCodeCamp.
There is no assignment, you can open a PR, after you have read out our guidelines

Discussion:
# --description-- <del> JavaScript is a powerful language which allows you to build websites that are interactive. To get started, create your standard HTML boilerplate with a `DOCTYPE`, `html`, `head`, and `body`. Include a `title` element and a `link` for your stylesheet, and your `meta` tag for the `charset`. Then, create a `div` element with the id `game` within your `body`. Use the text `RPG - Dragon Repeller` for your `title` element. </del> <ins> JavaScript is a powerful language which allows you to build websites that are interactive. To get started, create your standard HTML boilerplate with a `DOCTYPE`, `html`, `head`, and `body`. Include a `title` element and a `link` for your stylesheet, and your `meta` tag for the `charset`. Then, create a `div` element with `id` set to `game` within your `body`. Use the text `RPG - Dragon Repeller` for your `title` element. </ins> # --hints--
Change:
In the certification project pages, the tab on the left is "Instructions". However, if you resize the browser and the page switches to the mobile layout, the tab name changes to "Info". The "Console" on the desktop layout changes to "Tests" too. and other certification projects with built in editor to the browser Use the same name for the same content. ! ! Device: Laptop OS: Windows 10 Browser: Chrome Version: 108.0.5359.125 No response_
Technically, I don't think this is a WCAG failure. does address consistent identification of functional components. In this scenario, in wide view they are HTML buttons but in narrow view they are tabs, so technically they are not the same component and thus don't fall under 3.2.4. But for usability I would tend to agree that it would be best if they could use the same terminology since they basically do the same thing.
We can use "Console" for both mobile and desktop. Do we use "info" for the desktop layout and call it ?
I agree with using "Console" for both. For the panel showing user stories I would prefer using "Instructions" since the word "Info" seems too vague.
To solve this issue: use "Console" and "Instructions" for both layout. If you would like to fix this issue, please make sure you read , we prioritize contributors following the instructions in our guides. Join us in or if you need help contributing, our moderators will guide you through this.
We might want to keep in mind that is much longer than . We do not have much real-estate on mobile.
Here are words that I can think of are "details", "step", "story", "task", "manual", "guide", and "briefing". Is any of them good enough, or do we change the console for now and come back for "instructions" later?
My initial thought is: keep everything consistent, and just use the current mobile-naming for desktop as well. However, I am not entirely happy with the word for what it denotes. might be one option, but I also like your suggestion of .
I find or interesting . I vote for too, if no one else has issue with it, we can go with it, otherwise we go with .
I think is a term in agile development so I'm not sure if we can call it just . I would vote for or if is too long. However, my main concern was that the word changes as the user resizes the window. So, I'm okay with either of them as long as we use the same word for both layouts.
We decided to go with the desktop terms for both, "Instructions" and "Console". The file that needs to be changed is We are going to make another issue about improving the mobile UX to potentially use icons or another solution.
I think that should remain for responsive design issues on cell phones and since it is the appropriate term when the student goes to vsCode or another IDE

Discussion:
{!hasEditableBoundaries && ( <TabPane eventKey={Tab.Instructions} <del> title={i18next.t('learn.editor-tabs.info')} </del> <ins> title={i18next.t('learn.editor-tabs.instructions')} </ins> tabIndex={0} > {instructions}

</TabPane> <TabPane eventKey={Tab.Console} <del> title={i18next.t('learn.editor-tabs.tests')} </del> <ins> title={i18next.t('learn.editor-tabs.console')} </ins> {...editorTabPaneProps} > {testOutput}
Change:
In crowdin, I noticed that step 48 of the new JS course, build an rpg, uses a sentence that may need a grammar correction. Instead of “your button innerText” it should say “your buttons’ innerText”? Full sentence was: Grammar correction. No response N/A No response
Hello , Can you assign me this?
Should be changed to:
Thanks for opening this issue. This looks like something that can be fixed by "first-time" code contributors to this repository. Please make sure you read our , we prioritize contributors following the instructions in our guides. Join us in our or our if you need help contributing; our moderators will guide you through this. Sometimes we may get more than one pull request. We typically accept the most quality contribution followed by the one that is made first. Happy contributing.

Discussion:
# --description-- <del> In your `goTown` function, update your button `innerText` properties to be `Go to store`, `Go to cave`, and `Fight dragon`. Update your `onclick` properties to be `goStore`, `goCave`, and `fightDragon`, respectively. Finally, update your text's `innerText` property to be `You are in the town square. You see a sign that says Store.`. </del> <ins> In your `goTown` function, update your `button` elements' `innerText` properties to be `Go to store`, `Go to cave`, and `Fight dragon`. Update your `onclick` properties to be `goStore`, `goCave`, and `fightDragon`, respectively. Finally, update your text's `innerText` property to be `You are in the town square. You see a sign that says Store.`. </ins> # --hints--
Change:
The updated topic banner on the is covering up a couple of the table headers here <img width="1087" alt="Screen Shot 2023-01-03 at 9 51 13 PM" src="https://user-" to for a new update topic banner to show up on homepage. the issue There should be some space between the banner and the table headers in the forum like it was before. <img width="1112" alt="Screen Shot 2023-01-03 at 9 47 33 PM" src="https://user-"- Device: [mac book pro] OS: [MacOS] Browser: [ Chrome] No response
div id="ember47" class="categories-and-latest ember-view" Try adding a padding-top to this element. I used around 100px
this issue may be with the discourse forum, itself. If it's in the discourse forum and it's repeated in different forums, not just freeCodeCamp, then it should be solved there. Removing the below properties fixed it in my devtools.
I looked at the following communities that use discourse and didn't notice the problem there. At first glance, it looks like it is only on the fcc forum page.

Discussion:
| passport-linkedin-oauth2        | Sign-in with LinkedIn plugin.                                        | | passport-oauth                  | Allows you to set up your own OAuth 1.0a and OAuth 2.0 strategies.   | | request                         | Simplified HTTP request library.                                     | <del> | lodash                          | Handy JavaScript utlities library.                                   | </del> <ins> | lodash                          | Handy JavaScript utilities library.                                   | </ins> | uglify-js                       | Dependency for connect-assets library to minify JS.                  | | mocha                           | Test framework.                                                      | | chai                            | BDD/TDD assertion library.                                           |
Change:
Describe the bug Having special character in the slug, title, or heading of the challenges lead to broken structure as shown in the image below. Originally reported by ! These challenges are the translation of these. ! Although we can not add them in the Arabic translation, this is a fix to the side effect, because Arabic isn't the only RTL language with translation efforts. I think it's better to not include special characters in the heading, if they aren't wrapped in spaced, example 'the Logical And Operator &&'. So I suggest two solutions: Delete special character, if they aren't wrapped around spaces, like change "push()" to "push". Add code block around functions and methods, to be something like .
Would it be acceptable to spell these out a little more? Instead of We could do Not only do we get rid of the special characters but it possibly makes it a little clearer for people listening to the page.
In translation, that's perfectly fine . Good call.

Discussion:
--- id: 56bbb991ad1ed5201cd392cc <del> title: Manipulate Arrays With pop() </del> <ins> title: Manipulate Arrays With pop Method </ins> challengeType: 1 videoUrl: 'https://scrimba.com/c/cRbVZAB' forumTopicId: 18236

--- id: 56bbb991ad1ed5201cd392cb <del> title: Manipulate Arrays With push() </del> <ins> title: Manipulate Arrays With push Method </ins> challengeType: 1 videoUrl: 'https://scrimba.com/c/cnqmVtJ' forumTopicId: 18237

--- id: 56bbb991ad1ed5201cd392cd <del> title: Manipulate Arrays With shift() </del> <ins> title: Manipulate Arrays With shift Method </ins> challengeType: 1 videoUrl: 'https://scrimba.com/c/cRbVETW' forumTopicId: 18238

--- id: 56bbb991ad1ed5201cd392ce <del> title: Manipulate Arrays With unshift() </del> <ins> title: Manipulate Arrays With unshift Method </ins> challengeType: 1 videoUrl: 'https://scrimba.com/c/ckNDESv' forumTopicId: 18239