Change:
<!-- NOTE: If you're reporting a security issue, don't create a GitHub issue. Instead, email We will look into it immediately. --<!-- Add a link to the coding challenge with the problem. -- <!-- Copy and paste the code from the editor that you used in between the back-ticks below: --<!-- Add a clear and concise description of what you expected to happen. --in here should exist <code</codeelement: &lt;codesans-serif&lt;/code ! <!-- If applicable, add screenshots to help explain your problem. you can drag and drop, png, jpg, gif, etc. in this box. --<!-- Please complete the following information. --win11 Firefox Device: [e.g. iPhone6, Laptop] OS: [e.g. iOS 14, Windows 10, Ubuntu 20.4] Browser: [e.g. chrome, safari] Version: [e.g. 22] <!-- Add any other context about the problem here. --I want to modify it myselfbut I don't know how to deal with it. I don't know how to find him
Hi thanks for raising this issue, but there's nothing to fix here. The reason is that sans-serif is not being used as a programming term here, it is referring to the class of fonts. Multiple different fonts, such as Arial and Helvetica, fall into this class.
Hi@ Verdana similarly referring to the class of fonts, but please note picture, Verdana is surrounded <codeVerdana </code! in here should keep consistent
Thanks, that's a good point. I think Verdana should simply be plain text for consistency.
and The instruction to set the preferential font to is not a suggestion for a family of fonts. It is an instruction to use the code-word as the preferential font. It should remain within a element. Specifically, we are talking about family-names and generic-names : is not a generic-name font.
It's a bit of grey area, to be honest, but I feel like this is not really code. Reason being, it's just the name of specific font family called Verdana. It's not a keyword or part of any specific language, it just a string id that lets you get a via a rule.
Am I missing something? The challenge expects Campers to use the code , if they put anything else, it will fail. js const gs = (s) =new __helpers.CSSHelp(document).getStyle(s); const style = gs('h1, h2') gs('h2, h1'); assert.include(style?.fontFamily, 'Verdana'); `
and sans-serif both part of the actual css code !
My two cents, for what it's worth. I think Verdana should remain marked up as code since the instructions are specifically telling the user to use Verdana for the initial font. I've found other courses that have the font name marked up as code in the instructions as well. And it just seems that in general, whenever the instructions tell the user exactly what value to add, the value is marked up as code. And I also think that sans-serif should not be marked up as code since it is referring to a family of fonts and the tests will accept five different fonts for the fallback, so we aren't telling the user specifically what to use here. I'm guessing any confusion stems from the fact that one of the acceptable fall back fonts is sans-serif itself. Perhaps we could reword this a little? "..., and use another web-safe font in the sans-serif family as a fallback."
Thank you all very muchI understand itsans-serif is a family, Verdana is a sans-serif family menber. I think the suggestion is very good. <br !
Let's go with wording, I think that should be clearer than what we have.
How should I further locate where the file is !
is the file you need. We're in the process of making it easier to search for individual steps, but for now you can search for the title (Step 17 in this case) within that folder. For instance
&nbsp;thank you ---Original--- From: "Oliver Date: Fri, Apr 8, 2022 19:10 PM To: Cc: Subject: Re: [freeCodeCamp/freeCodeCamp] in here should exist <code&gt;</code&gt;element (Issue ) is the file you need. We're in the process of making it easier to search for individual steps, but for now you can search for the title (Step 17 in this case) within that folder. For instance grep -r 'Step 17' — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you were mentioned.Message ID:

Discussion:
Typeface plays an important role in the accessibility of a page. Some fonts are easier to read than others, and this is especially true on low-resolution screens. <del> Change the font for both the `h1` and `h2` elements to `Verdana`, and use another sans-serif _web safe_ font as a fallback. </del> <ins> Change the font for both the `h1` and `h2` elements to `Verdana`, and use another web-safe font in the sans-serif family as a fallback. </ins> Also, add a `border-bottom` of `4px solid #dfdfe2` to `h2` elements to make the sections distinct.