Build a Technical Documentation Page # 6 and #12

I’m getting two errors which I’m stumped on.

6. The .main-section elements should contain at least 5 elements total (not each).

12. Each element with the class of “nav-link” should contain text that corresponds to the text within each (e.g. if you have a “Hello world” section/header, your navbar should have an element which contains the text “Hello world”).

With the main-section element does that mean 5 bits of code under the html section? I haven’t used main-section as a .class but I did quickly try but still a fail.

All my nav-links do contain a elements that corresponds to each of the headers with #id. I’ve only done 5 nav-links, my plan was to copy the project as best I can and then design my own. I even put nav-links on all my li a elements and then linked them to all the headers on the page but still no go.

Any help greatly appreciated!

See the Pen Fork Me! FCC: Test Suite Template by Jamie (@jamtax) on CodePen.

Your browser information:

User Agent is: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.167 Safari/537.36.

Link to the challenge:

1 Like

6. The .main-section elements should contain at least 5 <code> elements total (not each).

You need to add

<code> Code blocks like these </code>

You made your own class called silverbox which looks great but the requirements are asking you to use code tags.

try this:

        <code>
          <p>function greetMe(yourName) {</p>
          <p>&emsp;alert("Hello " + yourName);</p>
          <p>}</p>
          <p>greetMe("World");</p>
        </code>

This would be one <code> element, you need 5 of them within a main-section class

4 Likes

‘What you should already know’ != ‘What you should know already’

Ohh ok, I didn’t even realise code was a tag! I was assuming it required at least 5 of any tag within the main-section.

Got to watch out for them typos…

Thank you camelcamper, really appreciate it!!!

3 Likes