Fix spelling and grammar mistakes in documentation (#1127)

* Initial plan

* Fix spelling and grammar mistakes in documentation

Co-authored-by: jbtronics <5410681+jbtronics@users.noreply.github.com>

---------

Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com>
Co-authored-by: jbtronics <5410681+jbtronics@users.noreply.github.com>

docs/usage/backup_restore.md

@@ -27,7 +27,7 @@ for more info about these options.
 
 ## Backup (manual)
 
-3 parts have to be backup-ed: The configuration files, which contain the instance-specific options, the
+3 parts have to be backed up: The configuration files, which contain the instance-specific options, the
 uploaded files of attachments, and the database containing the most data of Part-DB.
 Everything else like thumbnails and cache files, are recreated automatically when needed.
 
@@ -56,7 +56,7 @@ interface (`mysqldump -uBACKUP -pPASSWORD DATABASE`)
 ## Restore
 
 Install Part-DB as usual as described in the installation section, except for the database creation/migration part. You
-have to use the same database type (SQLite or MySQL) as on the backuped server instance.
+have to use the same database type (SQLite or MySQL) as on the backed up server instance.
 
 ### Restore configuration
 
@@ -71,7 +71,7 @@ Copy the `uploads/` and the `public/media/` folder from your backup into your ne
 
 #### SQLite
 
-Copy the backup-ed `app.db` into the database folder normally `var/app.db` in Part-DB root folder.
+Copy the backed up `app.db` into the database folder normally `var/app.db` in Part-DB root folder.
 
 #### MySQL / MariaDB
 

docs/usage/eda_integration.md

@@ -60,7 +60,7 @@ If you type in a character, you will get an autocomplete list of all symbols and
 
 ### Parts and category visibility
 
-Only parts and their categories, on which there is any kind of EDA metadata are defined show up in KiCad. So if you want to see parts in KiCad,
+Only parts and their categories on which there is any kind of EDA metadata defined show up in KiCad. So if you want to see parts in KiCad,
 you need to define at least a symbol, footprint, reference prefix, or value on a part, category or footprint.
 
 You can use the "Force visibility" checkbox on a part or category to override this behavior and force parts to be visible or hidden in KiCad.

docs/usage/getting_started.md

@@ -6,7 +6,7 @@ nav_order: 4
 
 # Getting started
 
-After Part-DB you should begin with customizing the settings, and setting up the basic structures.
+After Part-DB you should begin with customizing the settings and setting up the basic structures.
 Before starting, it's useful to read a bit about the [concepts of Part-DB]({% link concepts.md %}).
 
 1. TOC

docs/usage/import_export.md

@@ -49,7 +49,7 @@ You can upload the file that should be imported here and choose various options
   review" after the import. This can be useful if you want to review all imported parts before using them.
 * **Create unknown data structures**: If this is selected Part-DB will create new data structures (like categories,
   manufacturers, etc.) if no data structure(s) with the same name and path already exists. If this is not selected, only
-  existing data structures will be used and if no matching data strucure is found, the imported parts field will be empty.
+  existing data structures will be used and if no matching data structure is found, the imported parts field will be empty.
 * **Path delimiter**: Part-DB allows you to create/select nested data structures (like categories, manufacturers, etc.)
   by using a path (e.g. `Category 1->Category 1.1`, which will select/create the `Category 1.1` whose parent
   is `Category 1`). This path is separated by the path delimiter. If you want to use a different path delimiter than the

docs/usage/information_provider_system.md

@@ -78,7 +78,7 @@ results will be shown.
 ## Data providers
 
 The system tries to be as flexible as possible, so many different information sources can be used.
-Each information source is called am "info provider" and handles the communication with the external source.
+Each information source is called an "info provider" and handles the communication with the external source.
 The providers are just a driver that handles the communication with the different external sources and converts them
 into a common format Part-DB understands.
 That way it is pretty easy to create new providers as they just need to do very little work.
@@ -157,7 +157,7 @@ again, to establish a new connection.
 
 ### TME
 
-The TME provider uses the API of [TME](https://www.tme.eu/) to search for parts and getting shopping information from
+The TME provider uses the API of [TME](https://www.tme.eu/) to search for parts and get shopping information from
 them.
 To use it you have to create an account at TME and get an API key on the [TME API page](https://developers.tme.eu/en/).
 You have to generate a new anonymous key there and enter the key and secret in the Part-DB env configuration (see
@@ -176,10 +176,10 @@ The following env configuration options are available:
 
 ### Farnell / Element14 / Newark
 
-The Farnell provider uses the [Farnell API](https://partner.element14.com/) to search for parts and getting shopping
+The Farnell provider uses the [Farnell API](https://partner.element14.com/) to search for parts and get shopping
 information from [Farnell](https://www.farnell.com/).
 You have to create an account at Farnell and get an API key on the [Farnell API page](https://partner.element14.com/).
-Register a new application there (settings does not matter, as long as you select the "Product Search API") and you will
+Register a new application there (settings do not matter, as long as you select the "Product Search API") and you will
 get an API key.
 
 The following env configuration options are available:
@@ -191,7 +191,7 @@ The following env configuration options are available:
 
 ### Mouser
 
-The Mouser provider uses the [Mouser API](https://www.mouser.de/api-home/) to search for parts and getting shopping
+The Mouser provider uses the [Mouser API](https://www.mouser.de/api-home/) to search for parts and get shopping
 information from [Mouser](https://www.mouser.com/).
 You have to create an account at Mouser and register for an API key for the Search API on
 the [Mouser API page](https://www.mouser.de/api-home/).
@@ -226,7 +226,7 @@ An API key is not required, it is enough to enable the provider using the follow
 
 ### OEMsecrets
 
-The oemsecrets provider uses the [oemsecrets API](https://www.oemsecrets.com/) to search for parts and getting shopping
+The oemsecrets provider uses the [oemsecrets API](https://www.oemsecrets.com/) to search for parts and get shopping
 information from them. Similar to octopart it aggregates offers from different distributors.
 
 You can apply for a free API key on the [oemsecrets API page](https://www.oemsecrets.com/api/) and put the key you get

docs/usage/labels.md

@@ -6,7 +6,7 @@ parent: Usage
 
 # Labels
 
-Part-DB support the generation and printing of labels for parts, part lots and storage locations.
+Part-DB supports the generation and printing of labels for parts, part lots and storage locations.
 You can use the "Tools -> Label generator" menu entry to create labels or click the label generation link on the part.
 
 You can define label templates by creating Label profiles. This way you can create many similar-looking labels with for

docs/usage/tips_tricks.md

@@ -88,9 +88,9 @@ the user as "owner" of a part lot. This way, only he is allowed to add or remove
 
 ## Update notifications
 
-Part-DB can show you a notification that there is a newer version than currently installed available. The notification
+Part-DB can show you a notification that there is a newer version than currently installed. The notification
 will be shown on the homepage and the server info page.
-It is only be shown to users which has the `Show available Part-DB updates` permission.
+It is only shown to users which have the `Show available Part-DB updates` permission.
 
 For the notification to work, Part-DB queries the GitHub API every 2 days to check for new releases. No data is sent to
 GitHub besides the metadata required for the connection (so the public IP address of your computer running Part-DB).
@@ -98,6 +98,6 @@ If you don't want Part-DB to query the GitHub API, or if your server can not rea
 update notifications by setting the `CHECK_FOR_UPDATES` option to `false`.
 
 ## Internet access via proxy
-If you server running Part-DB does not have direct access to the internet, but has to use a proxy server, you can configure
+If your server running Part-DB does not have direct access to the internet, but has to use a proxy server, you can configure
 the proxy settings in the `.env.local` file (or docker env config). You can set the `HTTP_PROXY` and `HTTPS_PROXY` environment
 variables to the URL of your proxy server. If your proxy server requires authentication, you can include the username and password in the URL.