Add link to implementation instructions in tl;dr section

Author: webdevjeffus

README.md

@@ -8,7 +8,7 @@ The purpose of this how-to is to help you develop a flexible CSS stylesheet that
 However, this strategy is _not_ appropriate for styling anything beyond the MVP stage. Type-based selectors are measurably less performant than class-based or id-based selectors. While this isn't likely to noticeably affect performance on a locally-hosted app in development, it could have a perceivable impact on the performance of a large, publicly-deployed app served over the internet.
 
 ### TL;DR
-If you read this tutorial from beginning to end, you'll learn how to set up your own drop-in stylesheet and the compatible **layout** view. I'll explain what each CSS rule does, and why it does it. If you are in a hurry, you can skip down to the "Putting it in place" section and follow the instructions there to drop-in pre-generated .css and .erb files onto your app in just a few minutes. The pre-generated files will work fine, but you won't learn as much doing it that way. Your call.
+If you read this tutorial from beginning to end, you'll learn how to set up your own drop-in stylesheet and the compatible **layout** view. I'll explain what each CSS rule does, and why it does it. If you are in a hurry, you can skip down to the ["Putting it in place"](#putting-it-in-place) section and follow the instructions there to drop-in pre-generated .css and .erb files onto your app in just a few minutes. The pre-generated files will work fine, but you won't learn as much doing it that way. Your call.
 
 ## Setting up your HTML file
 For this to work, you need to set up your **layout.erb** (or **layout.html.erb**, in Rails) following some basic best-practices for semantic HTML. We'll be relying on HTML semantics to differentiate between tags of the same type in different areas of the page. For example, our stylesheet will handle an **\<h1>** tag differently if it appears in the app's **\<header>** element than if it is in the **\<main>**.