Merge pull request #764 from oalders/oalders/typos

Fix typos

Author: dlieou

BLOG-POST-TEMPLATE.md

@@ -188,7 +188,7 @@ At this time, the blog generates metadata in the following ways:
 - the `title` parameter in the blog post head generates the `<title></title>` tag
 - [OpenGraph meta tags](https://ogp.me/) are generated for social sharing
   - [`og:title`](https://ogp.me/#metadata) is populated with the `title` parameter in the [blog post head](#blog-head)
-  - [`og:description`](https://ogp.me/#optional) is populated with the first paragaph of the copy
+  - [`og:description`](https://ogp.me/#optional) is populated with the first paragraph of the copy
   - [`og:type`](https://ogp.me/#metadata) is populated with the value `"article"`
   - [`og:url`](https://ogp.me/#metadata) is populated with the URL of the article, which is derived from its path and filename
   - [`og:image`](https://ogp.me/#metadata) is populated with the `image` parameter in the [blog post head](#blog-head)

README.md

@@ -42,7 +42,7 @@ If you need help installing and/or managing Node and Yarn versions, check out [N
 npm install && npm run prepare
 ```
 
-- `npm install` installs the neccessary node modules for development.
+- `npm install` installs the necessary node modules for development.
 - `npm prepare` sets up the linting pre-commit hooks via husky.
 
 #### Install Hugo

content/2013/12/access-maxminds-web-services-via-ipv6.md

@@ -12,7 +12,7 @@ authors:
 
 We’re happy to announce that MaxMind’s roll out of Internet Protocol version 6
 (IPv6) access for our GeoIP2, Legacy GeoIP, Proxy Detection, and minFraud web
-service endpoints is complete. This update means each service is queriable at an
+service endpoints is complete. This update means each service is queryable at an
 [IPv6 address](https://en.wikipedia.org/wiki/IPv6_address) in addition to
 existing Internet Protocol version 4
 ([IPv4](https://en.wikipedia.org/wiki/IPv4)) addresses; no API updates are

content/2022/06/using-maxminds-accuracy-radius.md

@@ -68,7 +68,7 @@ One part of this application will use a customer’s geolocation to suggest the
 best local branch(es) to a customer, and automatically filter their search
 results based on that assumption.
 
-![A map of part of Massachussetts with several retail locations
+![A map of part of Massachusetts with several retail locations
 marked.](/images/2022/06/map-with-stores.png)
 
 Our application should leverage available customer preference and geolocation
@@ -132,7 +132,7 @@ When a new prospective customer visits our website, we check their IP
 geolocation. The GeoIP City Plus web service returns the geolocation coordinates
 42.1293, -72.7522.
 
-![The same map of Massachussetts with store branches marked, as above, but this
+![The same map of Massachusetts with store branches marked, as above, but this
 time there is also an IP geolocation point labeled on the map. The IP
 geolocation point on the map is located near a city named Springfield. There are
 store branches marked in Chicopee, near Springfield, but also further away to
@@ -144,7 +144,7 @@ that the customer is in a population center near the geographical coordinates,
 probably Springfield. We don’t really know where the customer is, but maybe this
 is what we expect:
 
-![The same map of Massachussetts with store branches and IP geolocation point
+![The same map of Massachusetts with store branches and IP geolocation point
 marked, as above, but this time there is also a marker for the actual customer
 location. The actual customer location marker is near the IP geolocation point
 marker, in the heart of Springfield, the largest town near the IP geolocation