User#13 Technical Documentation

Hi, im a bit struggling with this last criteria, i check the code and I don’t understand what I am doing wrong

##13When I click on a navbar element, the page should navigate to the corresponding section of the "main-doc" element (e.g. If I click on a "nav-link" element that contains the text "Hello world", the page navigates to a <section> element that has that id and contains the corresponding <header>.

thanks for your help!

Do you see where when you press on those nav menu items, you get a 404 error? That means it can’t go where you want, it doesn’t exist.

The issue is here:

    <li><a class="nav-link" href="Introduction"> Introduction</a></li>
    <li><a class="nav-link" href="Who_is_the_final_user"> Who is the final user</a></li>
    <li><a class="nav-link" href="Why_is_important"> Why is important</a></li>
    <li><a class="nav-link" href="Different_kind_of_technical_documents"> Different kind of technical documents</a></li>
    <li><a class="nav-link" href="Which_are_the_Benefits"> Which are the Benefits</a></li>
    <li><a class="nav-link" href="How_to_write_a_technical_document"> How to write a technical document</a></li>

The href tells the anchor where to go, and those are not valid destinations.

You could refer to the FCC lesson that taught you how to do this.
Or, you could use the secret weapon of every developer - google. Just google “html navigate to an id” and find the answer that way. (I cannot stress how much professional devs use google - no one can remember all of this stuff.)

With that knowledge, I was able to add one character to each of those lines and pass all of the tests.

Thank you! I found the mistake i was doing ( forgot to create a

in the destination) and the solution come from google because followinf FCC was keep giving the error!

Well, I was able to fix it doing what that FCC lesson taught. But if you found it, great. Congrats. Have fun on the next one.