Correct Typos and Enhance Clarity

docs/benchmark.md

@@ -23,7 +23,7 @@ The performance depends on two factors: the number of pageviews, and the number
 of unique paths you have. For example a site with 10M pageviews spread out over
 50 paths will be a lot faster than 1M pageviews spread out over 200,000 paths.
 
-The bencharks were run on the following configurations:
+The benchmarks were run on the following configurations:
 
 - Nanode 1GB, 1 core, $5/month
 - Linode 2GB, 1 core, $10/month

tpl/design.md

@@ -57,7 +57,7 @@ list is better for *most* users.
 
 Minimize clicks
 ---------------
-For example for example it shows the “day · month (..)” in the top navigation
+For example, it shows the “day · month (..)” in the top navigation
 as text links quite purposefully, as I find having them there within reach of
 a single click is easier than using a drop-down or some other more advanced UI
 widget. The more advanced widget would probably *look* better, but isn’t
@@ -68,7 +68,7 @@ Useful aggregate statistics rather than not-so-useful detailed statistics
 Chromium is just displayed as “Chrome”, as are Opera, Edge, and a bunch of other
 Chromium-based browsers. Do you *really* care if someone is using Chrome or
 Opera? The reason you care about this information is to be able to make informed
-decisions about browser and platform support. Since it’s the same same engine
+decisions about browser and platform support. Since it’s the same engine
 with the same behaviour, it doesn’t really matter.
 
 Similarly, Firefox on iOS is just displayed as Safari.

tpl/help/faq.md

@@ -8,7 +8,7 @@ seconds.</dd>
 <dd>No Referer was sent; this can mean that the user directly accessed the URL
 (e.g. from their bookmarks or typing it), that they disabled sending the Referer
 header, or that the link they clicked on disabled the Referer header with
-<code>rel="noreferer"</code>.</dd>
+<code>rel="noreferrer"</code>.</dd>
 
 
 <dt id="bots">How are bots and crawlers counted? <a href="#bots">§</a></dt>

tpl/help/frame.md

@@ -1,4 +1,4 @@
-Sometimes it may be useful to embed GoatCounter in a frame; by default ebedding
+Sometimes it may be useful to embed GoatCounter in a frame; by default embedding
 GoatCounter in a frame is disallowed, but in *Settings → Sites that can embed
 GoatCounter* you can add a list of domains or URLs that are allowed to embed
 GoatCounter.

tpl/help/js.md

@@ -3,7 +3,7 @@ is by far the easiest way to integrate GoatCounter, but other options are
 available too.
 
 The script is located at http://gc.zgo.at/count.js; although you can [host it
-somewhere else]({{.Base}}/code/countjs-host) if you want, and there are a
+somewhere else]({{.Base}}/code/countjs-host) if you want, and there are
 [stable versions]({{.Base}}/code/countjs-versions) that can use subresource
 integrity.
 
@@ -16,7 +16,7 @@ The script exposes `window.goatcounter` with various settings and methods.
 Settings
 --------
 The easiest way to set these is by setting the `data-goatcounter-settings`
-attribute on the `<script>` tag, but you can also set the on
+attribute on the `<script>` tag, but you can also set them on
 `window.goatcounter`. A few examples are listed below.
 
 The following settings are supported: