Merge branch '82-fix-service-template-typos' into 'master'

Fix typos in the service template (plus a few other small changes)

Closes #82

See merge request !62

docs/services/service-template.md

+# `<service_name>`
+
 This page gives an overview of the `<service_name>`, describing its current status, where and
 how it's developed and deployed, and who is responsible for maintaining it.
 
@@ -7,7 +9,7 @@ how it's developed and deployed, and who is responsible for maintaining it.
 
 ## Service Status
 
-The `<service_name>` is currently `pre alpha|alpha|beta|live|decommissioning`.
+The `<service_name>` is currently `pre-alpha|alpha|beta|live|decommissioning`.
 
 `<notes about status and links to roadmaps / timelines for future development or decommissioning>`
 
@@ -39,12 +41,12 @@ The source code for the `<service_name>` is spread over the following repositori
 | Repository  | Description
 | ----------- | ------------------ |
 | [Application Server]() | The source code for the main application server |
-| [Infratructure]()      | The Terraform infrastructure code for deploying the application server to GCP |
+| [Infrastructure Deployment]() | The Terraform infrastructure code for deploying the application server to GCP |
 
 
 ## Technologies used
 
-The following gives an overview of the `<service_name>` is built on.
+The following gives an overview of the technologies the `<service_name>` is built on.
 
 | Category | Language | Framework(s) |
 | -------- | -------- | --------- |
@@ -55,7 +57,7 @@ The following gives an overview of the `<service_name>` is built on.
 
 ## Operational documentation
 
-The following gives an overview of how the `<service_name>` is deployed and maintained
+The following gives an overview of how the `<service_name>` is deployed and maintained.
 
 ### How and where the `<service_name>` is deployed
 
@@ -86,8 +88,8 @@ The **service manager** for the `<service_name>` is `<service manager name and L
 
 The **tech lead** for the `<service_name>` is `<tech lead name and Lookup link>`.
 
-The following engineers have operational experience with `<service name>` and are able to respond
-to support requests or incidents:
+The following engineers have operational experience with the `<service_name>` and are able to
+respond to support requests or incidents:
 
 * `<engineer name and Lookup link>`
 * `<engineer name and Lookup link>`