Make small mods to heading structures in several WIPs

content/templates/taxonomy-templates.md

@@ -30,8 +30,6 @@ Hugo provides multiple ways to leverage taxonomies through your project:
 
 ### Lookup Order for Taxonomy List Templates
 
-
-
 ## Taxonomy Terms Template
 
 ### Lookup Order for Taxonomy Terms Templates

content/themes/creating-a-theme.md

@@ -15,7 +15,7 @@ needsreview: true
 ---
 
 {{% warning "Use Relative Links" %}}
-When creating your theme, it is not always safe to assume that the end user of the theme is working from the root directory of the website.
+When creating your theme, it is not always safe to assume that the end user of the theme is working from the root directory of the website. This is especially important for assets such as stylesheets. See [relURL](/functions/relurl) and [absURL](/functions/absurl).
 {{% /warning %}}
 
 Hugo has the ability to create a new theme in your themes directory for you
@@ -38,7 +38,7 @@ which are archetypal content types used by the `hugo new` command.
 The [`.Hugo.Generator`](/variables-and-params/other/) tag is included in all themes featured in the [Hugo Them Showcase](/http://themes.gohugo.io). We ask that you include the generator tag in all sites and themes you create with Hugo. The generator tag is significant in that it allows the Hugo team to track Hugo's usage and popularity.
 {{% /note %}}
 
-### Layouts
+## Layouts
 
 Hugo is built around the concept that things should be as simple as possible.
 Fundamentally website content is displayed in two different ways, a single
@@ -47,15 +47,15 @@ with the defaults. As additional layouts are defined they are used for the
 content type or section they apply to. This keeps layouts simple, but permits
 a large amount of flexibility.
 
-### Single Content
+## Single Content
 
 The default single file layout is located at `layouts/_default/single.html`.
 
-### List of Contents
+## List of Contents
 
 The default list file layout is located at `layouts/_default/list.html`.
 
-### Partial Templates
+## Partial Templates
 
 Theme creators should liberally use [partial templates](/templates/partials/)
 throughout their theme files. Not only is a good DRY practice to include shared
@@ -65,20 +65,23 @@ theme from their local /layouts. These partial templates are perfect for easy
 injection into the theme with minimal maintenance to ensure future
 compatibility.
 
-### Static
+## Static
 
 Everything in the static directory will be copied directly into the final site
 when rendered. No structure is provided here to enable complete freedom. It is
 common to organize the static content into:
 
-    /css
-    /js
-    /img
+```
+/css
+/js
+/img
+```
 
 The actual structure is entirely up to you, the theme creator, on how you would like to organize your files.
 
-### Archetypes
+## Archetypes
 
 If your theme makes use of specific keys in the front matter, it is a good idea
-to provide an archetype for each content type you have. Archetypes follow the
-[guidelines provided](/content/archetypes/).
+to provide an archetype for each content type you have. [Read more about archetypes][archetypes].
+
+[archetypes]: /content-management/archetypes/