Fix a few typos and other spelling issues

admin-manual/customization/config-files.rst

@@ -193,7 +193,7 @@ such as:
 .. IMPORTANT::
 
    Symfony (the PHP framework that AtoM uses) has a cascading system of
-   priorization for configuration files - if you create an ``app.yml`` file in
+   prioritization for configuration files - if you create an ``app.yml`` file in
    ``apps/qubit/config/``, its settings will override those found in
    ``config/app.yml``. This can be useful if you want to change some
    configuration values without actually altering AtoM's installation
@@ -302,7 +302,7 @@ index used in AtoM, including:
 * The normalizers, analyzers and filters used by Elasticsearch. See the
   `Elasticsearch`_ documentation for more information on these, and be sure
   you are looking at the documentation for the correct ES version
-* Number of shards and replicas created - these are paramters used for 
+* Number of shards and replicas created - these are parameters used for 
   performance optimization and scalability. See the `Elasticsearch`_ 
   documentation for more information
 * The tokenizers and filters used per culture - these can be useful to adjust
@@ -412,7 +412,7 @@ request originated, but this may not always work as expected when there are
 different domains or subdomains used, and can break the authentication procedure.
 
 To avoid this, system administrators can use the ``service_url`` parameter to
-specify the perferred service URL for your AtoM site that the CAS server
+specify the preferred service URL for your AtoM site that the CAS server
 should redirect users to after successfully completing authentication. 
 
 Example: 
@@ -685,7 +685,7 @@ Administrators can browse, view, edit, and delete storage records.
 * ``autocomplete``: Sets access to viewing matching containers when linking
   physical storage to other entities via the available autocomplete. See: 
   :ref:`link-physical-storage`.
-* ``boxList``: Sets access to the box list report, avaiable by clicking on the
+* ``boxList``: Sets access to the box list report, available by clicking on the
   printer icon on the view page of the related storage container. For more
   information, see: :ref:`storage-report-manage`.
 * ``browse``: Sets access to the physical storage browse page
@@ -720,7 +720,7 @@ and translator user groups, and delete permissions to the administrator group.
   modified. 
 * ``edit``: Sets access to the ability to modify existing static pages, and 
   create new ones
-* ``list``: Sets acess to the browse page for existing static pages. 
+* ``list``: Sets access to the browse page for existing static pages. 
 
 .. NOTE::
 
@@ -760,7 +760,7 @@ user groups. For a general overview of the AtoM header bar and its menus, see:
   that some top-level menu nodes cannot be deleted, just modified. 
 * ``edit``: Sets access to the ability to modify existing menu links, and 
   create new ones
-* ``list``: Sets acess to the menu management page listing all menus and nodes. 
+* ``list``: Sets access to the menu management page listing all menus and nodes. 
 
 .. NOTE::
 
@@ -837,4 +837,4 @@ changes will apply.
    * :ref:`read-only-mode`
    * :ref:`customization-authentication`
 
-:ref:`Back to top <customization-config-files>`
+:ref:`Back to top <customization-config-files>`

admin-manual/maintenance/cli-import-export.rst

@@ -1030,7 +1030,7 @@ for further tips and details on the uses of this option.
    You can always check what source name was used for records created via an
    import by entering into :term:`edit mode` and navigating to the
    Administration :term:` area <information area>` of the :term:`edit page` -
-   the source name used will be diplayed there:
+   the source name used will be displayed there:
 
    .. image:: images/source-name-ui.*
       :align: center
@@ -2405,7 +2405,7 @@ Finding the source name of a record
 You can always check in the user interface what source name was used for
 records created via an import by entering into :term:`edit mode` and navigating
 to the Administration :term:`area <information area>` of the :term:`edit page` -
-the source name used will be diplayed there:
+the source name used will be displayed there:
 
 .. image:: images/source-name-ui.*
    :align: center

user-manual/access-content/browse.rst

@@ -965,7 +965,7 @@ are viewing only the holdings of a particular institution.
    :alt: An image of an archival description browse page, limited to the holdings
          of a particular repository, with insittutional scoping enabled.
 
-You can remove the insitutional scoping and see all global browse results a
+You can remove the institutional scoping and see all global browse results a
 number of different ways:
 
 * By clicking the **X** on the :term:`filter tag` for the repository at the top
@@ -994,7 +994,7 @@ of the current :term:`repository`.
    :alt: An image of an institution block with the browse menu open
 
 If you follow these links, the institution block will remain visible on the
-related browse page, and if a background color has been applied to the instituion,
+related browse page, and if a background color has been applied to the institution,
 it will also be present on the browse page.
 
 .. TIP::
@@ -1168,7 +1168,7 @@ redirect you to a term view page, described below.
    and can be edited by authenticated (i.e. logged in) users with edit rights. For
    more information on the fields available and their uses, see:
    :ref:`term-data-entry`.
-6. Below the :term:`treeview`, addtional :term:`facet filters <facet filter>` that
+6. Below the :term:`treeview`, additional :term:`facet filters <facet filter>` that
    can be applied to the browse results are listed, if available. For more 
    information on using facet filters in AtoM, see: :ref:`recurring-facet-filters`.
 7. If a user is authenticated (i.e. logged in) and has edit permissions, a

user-manual/add-edit-content/archival-descriptions.rst

@@ -215,7 +215,7 @@ and types of users in AtoM see: :ref:`User roles <user-roles>`.
    description :term:`edit page`.
 
    One populated, you can still edit the supplied value - place your cursor in
-   the identiier :term:`field` and make any desired changes.
+   the identifier :term:`field` and make any desired changes.
 
    An :term:`administrator` can also turn on a setting so that the identifier
    field is pre-populated with a unique value, based on the
@@ -360,7 +360,7 @@ for more information on navigation in AtoM.
    You must be logged in to be able to create a new :term:`archival
    description` in AtoM. See: :ref:`Log in <log-in>`.
 
-1. In the :term:`view page` of the parent :term:`archival description`, scoll
+1. In the :term:`view page` of the parent :term:`archival description`, scroll
    to the bottom of the record to the :term:`button block` and click the "Add
    new" button.
 
@@ -1078,7 +1078,7 @@ used within the cultural heritage community. For more information on
 standards used in AtoM, see: :ref:`descriptive-standards`.
 
 You can change the :term:`display standard` for an individual archival
-description in the adminstration area while editing an archival description.
+description in the administration area while editing an archival description.
 This allows you to choose a different description template per archival
 description than the template you have chosen in your AtoM
 :ref:`settings <default-templates>`. This includes at different levels of the
@@ -1414,7 +1414,7 @@ the filename of a linked digital object will be covered on the
    notification banner will appear at the top of the page acknowledging your
    edits. If the value you have entered for the slug has been changed by AtoM
    (e.g. sanitized to remove special characters, spaces, or capital letters,
-   or incremented to make the slug uniqe), the message will mention this so
+   or incremented to make the slug unique), the message will mention this so
    you can review the slug in your browser's address bar.
 
 .. image:: images/rename-slug-warning-banner.*
@@ -1505,7 +1505,7 @@ so:
      Note that for administrators, these usernames will appear as hyperlinks - an
      administrator can click the hyperlink to navigate to the related user's 
      :term:`profile <user profile>` page, where a full history of that user's 
-     desrciption modifications can be seen. For more information, see: 
+     description modifications can be seen. For more information, see: 
      :ref:`user-modification-history`. 
 
 .. image:: images/mod-history-1.*
@@ -1718,7 +1718,7 @@ lower level of description can also be moved so that it becomes a new
    orient yourself, a :term:`breadcrumb trail` will appear above the list of
    potential archival descriptions, indicating where in the
    :term:`archival unit's <archival unit>` you are currently located - this is
-   intented to help Users understand if they are moving the record to
+   intended to help Users understand if they are moving the record to
    a subfonds, series, sub-series, or a file.
 
 .. image:: images/move-breadcrumb.*

user-manual/add-edit-content/archival-institutions.rst

@@ -198,8 +198,8 @@ archival institution in :term:`edit mode`.
 
 .. _add-institution-description-edit:
 
-Add a new archival instituion from an archival description edit page
---------------------------------------------------------------------
+Add a new archival institution from an archival description edit page
+---------------------------------------------------------------------
 
 A new archival institution can be generated from an :term:`archival description`
 record at any time; it does not first have to be created separately.
@@ -436,7 +436,7 @@ populated based on data entered into the "Type" :term:`field` in the Identity
 
 The **Geographic subregion** and **Thematic area** facets are managed as
 :term:`access points <access point>`, and must be manually added in the
-Access points :term:`area <information area>` of the archival institiution
+Access points :term:`area <information area>` of the archival institution
 :term:`edit page`. Similar to the :term:`place` and :term:`subject` access point
 fields available on :term:`archival descriptions <archival description>`, all
 access points included by default or added by users are managed as
@@ -695,7 +695,7 @@ Change the background color of an archival institution
 This new design feature allows authenticated (i.e. logged in)
 :term:`administrators <administrator>` to customize their archival institution
 record by changing the background color of the page. Users can choose and
-modify (i.e. hue, tint) a color from a pre-determined color pallette.
+modify (i.e. hue, tint) a color from a pre-determined color palette.
 Changing the background color in an archival institution :term:`edit page`
 will automatically change the background color of all the :term:`archival
 description` pages linked to that specific institution.
@@ -743,8 +743,8 @@ description` pages linked to that specific institution.
    background for all related :term:`archival descriptions
    <archival description>` as well. Use the slider on the right of the
    :term:`color picker` drop-down to select a **hue** - you can click or drag
-   the slider bar to dynamically change the color in the pallette. Use the
-   pallette to select a **tint** - you can click or drag in the pallette to
+   the slider bar to dynamically change the color in the palette. Use the
+   palette to select a **tint** - you can click or drag in the palette to
    dynamically change the color. There is also a text-box provided where you
    can manually enter a :term:`hex color code` if you with. The selected
    color will be displayed in the small preview box next to the
@@ -782,7 +782,7 @@ Add/edit a logo to an existing archival institution
 Authenticated (i.e. logged in) :term:`administrators <administrator>` also have
 the option to customize the :term:`archival institution` record by adding a logo
 to the institution's page. Below are instructions to :ref:`add a logo
-<add-logo>` and :ref:`edit and/or delete an exisiting logo <edit-logo>` for an
+<add-logo>` and :ref:`edit and/or delete an existing logo <edit-logo>` for an
 archival institution.
 
 .. _add-logo:
@@ -860,10 +860,10 @@ appearing above the name of the archival institution, as well as on any
 
 .. _edit-logo:
 
-Edit/remove an exisiting logo for an archival institution
+Edit/remove an existing logo for an archival institution
 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
 
-**To edit an exisiting logo:**
+**To edit an existing logo:**
 
 1.  Navigate to the :term:`archival institution` you wish to edit. You can do
     this by :doc:`browsing <../access-content/browse>` or
@@ -885,7 +885,7 @@ Edit/remove an exisiting logo for an archival institution
    :alt: An image of the edit theme button in the button block
 
 3.  From here, navigate to the "Style" area, under the "Logo" :term:`field`,
-    click the "Browse" button under the exisiting logo.
+    click the "Browse" button under the existing logo.
 
 .. image:: images/upload-new-logo.*
    :align: center
@@ -966,7 +966,7 @@ Once uploaded, the banner will appear on the archival institution's :term:`view
 page`, below the institution's name. Unlike the institution's logo, the banner
 will *not* appear on any :term:`archival description` pages linked to the
 archival institution. Below are instructions to :ref:`add a banner <add-banner>`
-and :ref:`edit and/or delete an exisiting banner <edit-banner>` for an archival
+and :ref:`edit and/or delete an existing banner <edit-banner>` for an archival
 institution.
 
 .. _add-banner:
@@ -1058,7 +1058,7 @@ Edit/remove an existing banner for an archival institution
    :alt: An image of the edit theme button in the button block
 
 3.  From here, navigate to the "Style" area, under the "Logo" :term:`field`,
-    click the "Choose file" button under the exisiting logo.
+    click the "Choose file" button under the existing logo.
 4.  A separate window will open; select the image on your computer that you'd
     like to replace the existing banner with. See the :ref:`previous section
     <banner-size-requirements>` for direction on AtoM **sizing requirements**
@@ -1223,7 +1223,7 @@ the :term:`user interface`.
 
 3. Navigate to |gears| **Admin > Settings** and scroll down to near the bottom
    of the Global settings page. Add your Maps API key to the field marked
-   "Google Maps Javascript API key setting." For more information, see:
+   "Google Maps JavaScript API key setting." For more information, see:
    :ref:`maps-api-key`. Don't forget to save your settings after making
    changes, using the :term:`button block` at the bottom of the Settings page.
 
@@ -1313,7 +1313,7 @@ left-hand side of the institution's page.
    :width: 50%
    :alt: An image of the archival institution upload limit settings
 
-3. A dialogue box will apear that will allow for 1 of 3 options:
+3. A dialogue box will appear that will allow for 1 of 3 options:
 
    * **Disable uploads** will prevent users from uploading any
      :term:`digital objects <digital object>`.

user-manual/add-edit-content/authority-records.rst

@@ -910,7 +910,7 @@ From the authority record
    remove the relationship link. You can also repeat this process to add
    multiple links by clicking the "Add new" button below the Related
    resources again - AtoM will open a new pop-up dialog. Repeat steps 3-7 as
-   needed. If more desccriptions have been linked than the global 
+   needed. If more descriptions have been linked than the global 
    :ref:`results per page <results-page>` setting (which defaults to 10 in new 
    installations), AtoM will add a pager - you can click "Show more" button 
    below the list of linked descriptions to load the next set

user-manual/add-edit-content/control-area.rst

@@ -209,8 +209,8 @@ Sources
 "Record the sources consulted in establishing the description." ISDIAH 5.6.8,
 ISAAR 5.4.8, ISDF 5.4.8
 
-"Record relevant information about sources conslulted in establishing or
-revising the description." DACS 8.1.3. **Note** that this field is labeled
+"Record relevant information about sources consulted in establishing or
+revising the description." DACS 8.1.3. **Note** that this field is labelled
 "Sources used" in the :ref:`DACS template <dacs-template>`.
 
 .. image:: images/control-area-sources.*
@@ -254,7 +254,7 @@ prepared it." ISAD 3.7.1
 
 "Record the name(s) of the person(s) who created or revised the description,
 as well as the creation or revision date." DACS 8.1.5. **Note** that this
-field is labeled "Archivist and date" in the
+field is labelled "Archivist and date" in the
 :ref:`DACS template <dacs-template>`.
 
 .. image:: images/control-area-archivists-notes.*

user-manual/add-edit-content/deaccessions.rst

@@ -24,7 +24,7 @@ practice.
 In AtoM, a :term:`deaccession record` can be added to an existing
 :term:`accession record`. The deacession record comprises several basic
 fields to capture information about the materials being deaccession and the
-reasons behind the deaccssion. Fields include:
+reasons behind the deaccession. Fields include:
 
 * Deaccession number
 * Scope (whole accession, or only part)

user-manual/add-edit-content/donors.rst

@@ -8,13 +8,13 @@ The `SAA Glossary <http://www2.archivists.org/glossary>`__ defines a donor as
 "*An individual or organization who gives property or money to another without
 reciprocal compensation,*" adding that in many instances, "*individuals who
 donate collections are not the provenance of the collection.*" This implies
-that a donor is not nessarily the :term:`creator` of the materials being
+that a donor is not necessarily the :term:`creator` of the materials being
 donated to a :term:`repository` - rather, they are the last legal custodian of
 the records before they are passed to a :term:`repository` for long-term
 preservation.
 
 In AtoM, donor records can be used more generically than the SAA Glossary
-defintion - they can be used to manage records of all individuals who supply
+definition - they can be used to manage records of all individuals who supply
 records and other materials to a repository, whether freely or with the
 expectation of compensation. Donor records are a way to maintain a record of
 the provenance of :ref:`accessions <accession-records>`, so that donors can be
@@ -85,7 +85,7 @@ Using the donor dialog in the accessions template
    :alt: An image of the Manage menu
 
 2. In the :term:`accession record` :term:`edit page`, Navigate to the
-   "Donor/Trasferring body" :term:`information area` and click the "Add new"
+   "Donor/Transferring body" :term:`information area` and click the "Add new"
    button.
 
 .. image:: images/add-new-donor.*
@@ -109,7 +109,7 @@ Using the donor dialog in the accessions template
    complete the related fields in the dialog as needed. Fields available in
    the :term:`donor dialog` include:
 
-   * **Name** - an autcomplete field where you can link to an existing donor
+   * **Name** - an autocomplete field where you can link to an existing donor
      record or enter a new name to create a new donor record.
    * **Main tab:**
 
@@ -136,7 +136,7 @@ Using the donor dialog in the accessions template
 
    When new information is entered into the :term:`donor dialog`, a new Donor
    record is created. Alternatively, if you have selected an existing donor
-   using the autcomplete values in the Name field, you can edit the existing
+   using the autocomplete values in the Name field, you can edit the existing
    contact information.
 
 5. Once you have completed entering the donor information, click on the
@@ -342,7 +342,7 @@ that you would like to associate with the donor. To do so:
    :term:`information areas <information area>` closed; click on an
    information area to access the :term:`fields <field>` grouped under it.
 5. In the :term:`accession record` :term:`edit page`, Navigate to the
-   "Donor/Trasferring body" :term:`information area` and click the "Add new"
+   "Donor/Transferring body" :term:`information area` and click the "Add new"
    button.
 
 .. image:: images/add-new-donor.*