Fix a few misspellings

docs/alpaca/alpaca-technical-stack.md

@@ -1,5 +1,5 @@
 # Alpaca Technical Stack
-As of version 2.0.0, Alpaca contains serveral tools bundled into a single runnable [jar](https://en.wikipedia.org/wiki/JAR_(file_format)) file. The different tools can be enabled/disabled depending on the configuration you define.
+As of version 2.0.0, Alpaca contains several tools bundled into a single runnable [jar](https://en.wikipedia.org/wiki/JAR_(file_format)) file. The different tools can be enabled/disabled depending on the configuration you define.
 
 ## [Gradle](https://docs.gradle.org/current/userguide/tutorial_using_tasks.html)
 Gradle is used by Alpaca as a build and package management tool. It is similar to [Maven](https://maven.apache.org/).

docs/installation/docker-custom.md

@@ -98,7 +98,7 @@ certificate authority.  As long as the certificates match the `DOMAIN` variable
 
 | File | Purpose |
 | :---- | :------- |
-| __cert.pem__     | A PEM encoded certificate that also contains the issuer's certificate as well. Most certificate authorities offer "Full Chain" or "With Issuer" certificates that contain everything you need.  Occassionally, you may find yourself needing to manually concatenate your certificate with the issuer certificate by hand. In that case, the certificate for your site goes first, and the issuer's certificate is appended afterwards. |
+| __cert.pem__     | A PEM encoded certificate that also contains the issuer's certificate as well. Most certificate authorities offer "Full Chain" or "With Issuer" certificates that contain everything you need.  Occasionally, you may find yourself needing to manually concatenate your certificate with the issuer certificate by hand. In that case, the certificate for your site goes first, and the issuer's certificate is appended afterwards. |
 | __privkey.pem__  | A PEM encoded private key used to sign your certificate |
 
 
@@ -132,7 +132,7 @@ You'll still get security exceptions when it's working, but you should be able t
 If you are still getting security exceptions, check what certificate is being used through your browser.  Setting `TRAEFIK_LOG_LEVEL=DEBUG` in your `.env` file will help out greatly when debugging Traefik.  You can tail the logs with `docker-compose logs -tf traefik`.
 
 #### traefik.me SSL certificate expired or revoked
-The _*.traefik.me_ certificate that covers `islandora.traefik.me` will need to be redownloaded ocassionally, due to the certificate expiring or possibly being revoked. You can download the updated certificates by performing the following commands:
+The _*.traefik.me_ certificate that covers `islandora.traefik.me` will need to be redownloaded occasionally, due to the certificate expiring or possibly being revoked. You can download the updated certificates by performing the following commands:
 
 ```
 rm certs/cert.pem
@@ -143,9 +143,9 @@ docker-compose restart traefik
 
 !!! note "traefik.me Certificate Note"
 
-    Please note that sometimes the upstream provider of the traefik.me certificate takes a couple of days to update the certificiate after it expires or is accidently revoked.
+    Please note that sometimes the upstream provider of the traefik.me certificate takes a couple of days to update the certificate after it expires or is accidentally revoked.
 
-### Requesting Certifcates through ACME and External Account Binding
+### Requesting Certificates through ACME and External Account Binding
 
 To request certificates through another Certificate Authority (CA) that supports External Accounting Binding through ACME such as InCommon or ZeroSSL you will need to add the following to your `.env` file:
 
@@ -157,7 +157,7 @@ ACME_EAB_KID=
 ACME_EAB_HMAC=
 ```
 
-Where `ACME_SERVER` is the CA server to use, `ACME_EAB_KID` is the key identifer from the External CA, and `ACME_EAB_HMAC` is the HMAC key from the External CA.
+Where `ACME_SERVER` is the CA server to use, `ACME_EAB_KID` is the key identifier from the External CA, and `ACME_EAB_HMAC` is the HMAC key from the External CA.
 
 Once you have added these commands you will need to run the following commands:
 

docs/installation/manual/installing_composer_drush_and_drupal.md

@@ -60,7 +60,7 @@ composer create-project drupal/recommended-project my-project
 Before we can proceed with the actual site installation, we’re going to need to make our new Drupal installation the default web-accessible location Apache serves up. This will include an appropriate `ports.conf` file, and replacing the default enabled site.
 
 !!! notice
-    Out of the box, these files will contain support for SSL, which we will not be setting up in this guide (and therefore removing with these overwritten configurations), but which are **absolutely indispensible** to a production site. This guide does not recommend any particular SSL certificate authority or installation method, but you may find [DigitalOcean's tutorial](https://www.digitalocean.com/community/tutorials/how-to-install-an-ssl-certificate-from-a-commercial-certificate-authority) helpful.
+    Out of the box, these files will contain support for SSL, which we will not be setting up in this guide (and therefore removing with these overwritten configurations), but which are **absolutely indispensable** to a production site. This guide does not recommend any particular SSL certificate authority or installation method, but you may find [DigitalOcean's tutorial](https://www.digitalocean.com/community/tutorials/how-to-install-an-ssl-certificate-from-a-commercial-certificate-authority) helpful.
 
 `/etc/apache2/ports.conf | root:root/644`
 ```
@@ -117,7 +117,7 @@ grant all privileges on database DRUPAL_DB to DRUPAL_DB_USER;
 
 ## Install Drupal using Drush
 
-The Drupal installation process can be done through the GUI in a series of form steps, or can be done quickly using Drush's `site-install` command. It can be invoked with the full list of parameters (such as `--db-url` and `--site-name`), but if parameters are missing, they will be asked of you interactiveley.
+The Drupal installation process can be done through the GUI in a series of form steps, or can be done quickly using Drush's `site-install` command. It can be invoked with the full list of parameters (such as `--db-url` and `--site-name`), but if parameters are missing, they will be asked of you interactively.
 
 ### Option 1: Site install the Starter Site with existing configs
 

docs/tutorials/create_update_views.md

@@ -61,7 +61,7 @@ For this example, we create a new view that only shows collections. It will be c
 4.	Name the view and select **Create a block**. Give the block a title and decide how you want it to display (Grid, Table, List, Paging). To progress, select **Save and edit**.
 
     ![Frontpage view collection list information](../assets/frontpage_view_collection_list_info.png)
-5.	Customise the view format and sorting as required.
+5.	Customize the view format and sorting as required.
 6.	Add a _filter criteria_ to only show the Islandora model type of 'Collection' and **Save** the view.
 
     ![Frontpage view collection list details](../assets/frontpage_view_collection_list_details.png)

docs/user-documentation/access-control.md

@@ -112,7 +112,7 @@ Both are enabled out of the box in the Islandora Starter Site. This will ensure
 
 "The [Permissions by Term](https://www.drupal.org/project/permissions_by_term) module extends Drupal by functionality for restricting view and edit access to single nodes  via taxonomy terms. [...] Taxonomy term permissions can be coupled to specific user accounts and/or user roles." By default, this module only affects nodes. To enable Permissions by Term for Media and other entities, enable the "Permissions by Entity" submodule.
 
-The Islandora Starter Site includes an empty vocabulary called "Islandora Access", which is intended to hold such taxonomy terms. However, permissions_by_term or a similar mechanism to controll access must be installed and configured on your own.
+The Islandora Starter Site includes an empty vocabulary called "Islandora Access", which is intended to hold such taxonomy terms. However, permissions_by_term or a similar mechanism to control access must be installed and configured on your own.
 
 This module is known to work, and appears to be supported well by the Drupal community.
 

docs/user-documentation/content_models.md

@@ -187,7 +187,7 @@ This document was originally developed by [Alex Kent](https://github.com/alexken
 
 [^1] In the Islandora Starter Site, this is the `field_model` field, which is populated by taxonomy terms in the `islandora_models` taxonomy vocabulary provided by the `islandora_core_feature` submodule of `Islandora/islandora`
 
-[^2] In the Islandora Starter Sitee, this is the `field_member_of` field.
+[^2] In the Islandora Starter Site, this is the `field_member_of` field.
 
 ## Islandora Legacy Objects versus Islandora Resource Nodes
 

docs/user-documentation/content_types.md

@@ -97,7 +97,7 @@ Your custom content types can contain whatever fields you like, but there are tw
 
 1. In order for a custom content type to be considered an Islandora Object, it needs to have the field "Member of" ('field_member_of'). This allows it to be included in contexts that have the "Node is an Islandora node" condition. Nodes that have this field will automatically be synced to Fedora and indexed by the triple store if you are using the context provided by the Islandora Starter Site. Having this field present in your content type also gives you tabs for adding children and media when viewing an item of that content type.
 
-2. The other mandatory field is "Model" ('field_model'). This is used in several of the contexts that the Islandora Starter Site provides. This field determines how Islandora objects are diplayed, and how media derivatives are created.
+2. The other mandatory field is "Model" ('field_model'). This is used in several of the contexts that the Islandora Starter Site provides. This field determines how Islandora objects are displayed, and how media derivatives are created.
 
 ## Updating and creating an RDF Mapping
 

docs/user-documentation/glossary.md

@@ -205,7 +205,7 @@ See https://www.drupal.org/docs/8/core/modules/media/overview for more informati
 Protocol specification that allows a web client to request an earlier/historic state web resource (if available). Fedora implements the Memento protocol to store and serve versions of content in a Fedora repository.
 
 ## Mirador
-[Mirador](https://projectmirador.org) is a javascript-based zoomable image [Viewer](#viewer). It is related to (and more fully-featured than) [OpenSeadragon](#openseadragon). It has the ability to do zooming, display multiple pages, and display positioned text (e.g. [hOCR](#hocr) or attributions). To render an image through Mirador, it must be provied in a [IIIF Manifest](#iiif-manifest) and the images must be served through a [IIIF](#iiif)-friendly image server such as [Cantaloupe](#cantaloupe).
+[Mirador](https://projectmirador.org) is a javascript-based zoomable image [Viewer](#viewer). It is related to (and more fully-featured than) [OpenSeadragon](#openseadragon). It has the ability to do zooming, display multiple pages, and display positioned text (e.g. [hOCR](#hocr) or attributions). To render an image through Mirador, it must be provided a [IIIF Manifest](#iiif-manifest) and the images must be served through a [IIIF](#iiif)-friendly image server such as [Cantaloupe](#cantaloupe).
 
 ## Microservice
 A software development technique — a variant of the service-oriented architecture (SOA) structural style — that arranges an application as a collection of loosely coupled services. In a microservices' architecture, services are fine-grained and the protocols are lightweight.