Docs: fix some typos in templates/variables.md

diff --git a/docs/content/templates/variables.md b/docs/content/templates/variables.md
index 18e933f5d74949f76df79ff4d36bb43c729b89bd..2f0a2279b765401b0cc892a25dd7a9f0d4f711a3 100644 (file)
--- a/docs/content/templates/variables.md
+++ b/docs/content/templates/variables.md
@@ -71,13 +71,13 @@ This is particularly useful for the introduction of user defined fields in conte
 
     ---
        ...
-    affiliatelnk: "http://www.my-book-link.here"
+    affiliatelink: "http://www.my-book-link.here"
        recommendedby: "my Mother"
     ---
 
-Which would then be accessible to a template at <code>/theme/yourtheme/review/single.html</code>, for example, through <code>.Params.affiliatelnk</code> and <code>.Params.recommendedby</code>, respectively. Two common situations where these could be introduced are as a value of a certain attribute (like <code>href=""</code> below) or by itself if it will be displayed. Sample syntaxes include:
+Which would then be accessible to a template at `/theme/yourtheme/review/single.html`, for example, through `.Params.affiliatelink` and `.Params.recommendedby`, respectively. Two common situations where these could be introduced are as a value of a certain attribute (like `href=""` below) or by itself if it will be displayed. Sample syntaxes include:
 
-    <h3><a href="{{ printf "%s" $.Params.affiliatelnk }}">Buy this book</a></h3>
+    <h3><a href="{{ printf "%s" $.Params.affiliatelink }}">Buy this book</a></h3>
        <p>It was recommended by {{ .Params.recommendedby }}.</p>
 
 which would render
@@ -85,7 +85,7 @@ which would render
     <h3><a href="http://www.my-book-link.here">Buy this book</a></h3>
        <p>It was recommended by my Mother.</p>
 
-**See also:** [cross-references]({{% ref "content/archetypes.md" %}}) for consistency of `Params` accross pieces of content.
+**See also:** [cross-references]({{% ref "content/archetypes.md" %}}) for consistency of `Params` across pieces of content.
 
 ### Param method
 In Hugo you can declare params both for the site and the individual page.  A common use case is to have a general value for the site and a more specific value for some of the pages (i.e. an image).