Fix typos and grammar errors in documentation (#5506)

* fix: correct typos and grammar errors in documentation

* revert

* Lint

---------

Co-authored-by: Olga Bulat <[email protected]>

Author: huzaifaalmesbah

documentation/api/guides/documentation.md

@@ -13,7 +13,7 @@ Framework API.
 
 - Run the server locally by following the [API quickstart guide](quickstart.md)
 - Update documentation
-- Make sure the updates passed the automated tests in defined in our
+- Make sure the updates passed the automated tests defined in our
   [CI/CD workflow](/meta/ci_cd/index.md)
 - Commit and push
 - Create pull request by following our

documentation/api/reference/search_algorithm.md

@@ -6,7 +6,7 @@ documentation on this page was written by referencing the code in Openverse as
 well as parts of Openverse's historical development. Parts of the story for how
 Openverse's indexes came to be configured as they are today are likely missing.
 Future improvements to Openverse's indexing and search will be more carefully
-documented here and in the code to ensure there is greater longevitiy of
+documented here and in the code to ensure there is greater longevity of
 understanding.
 
 > **Note**: This document avoids covering details covered in the
@@ -23,7 +23,7 @@ about Elasticsearch, full text-search, and Openverse's index configuration:
 - [Elasticsearch 7.12 documentation](https://www.elastic.co/guide/en/elasticsearch/reference/7.12/index.html)
 - [Full-text search (Wikipedia)](https://en.wikipedia.org/wiki/Full-text_search)
 - [Stemming (Wikipedia)](https://en.wikipedia.org/wiki/Stemming)
-- [`es_mapping.py` (index configuration)](https://github.com/WordPress/openverse-api/blob/main/ingestion_server/ingestion_server/es_mapping.py)
+- [`es_mapping.py` (index configuration)](https://github.com/WordPress/openverse/blob/main/ingestion_server/ingestion_server/es_mapping.py)
 
 ## Terms
 
@@ -211,8 +211,8 @@ These are the fields currently supported for individual field querying:
 
 Each of these can be stacked. You can make a request that queries for a specific
 title by a specific creator. The following parameters would search only for
-works by "Claude Monet" where the word "madame" (or it's stemmed versions)
-appear in the title: `?creator=Claude Monet&title=madame`.
+works by "Claude Monet" where the word "madame" (or its stemmed versions) appear
+in the title: `?creator=Claude Monet&title=madame`.
 
 As you can see, this is unique from the general query searching in that it
 allows you to apply separate queries for individual fields (hence the name

documentation/catalog/guides/adding_a_new_provider.md

@@ -12,7 +12,7 @@ generated for each provider. A simple provider DAG looks like this:
 
 At a high level the steps are:
 
-1. `generate_filename`: Generates the named of a TSV (tab-separated values) text
+1. `generate_filename`: Generates the name of a TSV (tab-separated values) text
    file that will be used for saving the data to the disk in later steps
 2. `pull_data`: Pulls records from the provider API, collects just the data we
    need, and commits it to local storage in TSVs.

documentation/frontend/guides/analytics.md

@@ -50,7 +50,7 @@ Plausible supports custom events via its "goals" feature.
 
 Sending custom events to Plausible is done by calling the `sendCustomEvents`
 function. For this function to accept a custom event name, you must update the
-`Events` type in `frontend/src/types/analyticts.ts` to include the new event
+`Events` type in `frontend/shared/types/analytics.ts` to include the new event
 name and any payload elements unique to the event.
 
 Custom events must be added to Plausible for it to record them. You may do this