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/upgrade/1_to_2.md

@@ -27,7 +27,7 @@ about the requirements at all.
 
 ## Changes
 * Configuration is now preferably done via a web settings interface. You can still use environment variables, these overwrite
-the settings in the web interface. Existing configuration will still work, but you should consider migriting them to the
+the settings in the web interface. Existing configuration will still work, but you should consider migrating them to the
 web interface as described below.
 * The `config/banner.md` file that could been used to customize the banner text, was removed. You can now set the banner text
   directly in the admin interface, or by setting the `BANNER` environment variable. If you want to keep your existing
@@ -43,7 +43,7 @@ The upgrade process works very similar to a normal (minor release) upgrade.
 
 ### Direct installation
 
-**Be sure to execute the following steps as the user that owns the Part-DB files (e.g. `www-data`, or your webserver user). So prepend a `sudo -u wwww-data` where necessary.**
+**Be sure to execute the following steps as the user that owns the Part-DB files (e.g. `www-data`, or your webserver user). So prepend a `sudo -u www-data` where necessary.**
 
 1. Make a backup of your existing Part-DB installation, including the database, data directories and the configuration files and `.env.local` file.
 The `php bin/console partdb:backup` command can help you with this.
@@ -51,7 +51,7 @@ The `php bin/console partdb:backup` command can help you with this.
 3. Remove the `var/cache/` directory inside the Part-DB installation to ensure that no old cache files remain.
 4. Run `composer install --no-dev -o` to update the dependencies.
 5. Run `yarn install` and `yarn build` to update the frontend assets.
-6. Rund `php bin/console doctrine:migrations:migrate` to update the database schema.
+6. Run `php bin/console doctrine:migrations:migrate` to update the database schema.
 7. Clear the cache with `php bin/console cache:clear`.
 8. Open your Part-DB instance in the browser and log in as an admin user.
 9. Go to the user or group permissions page, and give yourself (and other administrators) the right to change system settings (under "System" and "Configuration").
@@ -79,7 +79,7 @@ To change it, you must migrate your environment variable configuration to the ne
 
 For this there is the new console command `settings:migrate-env-to-settings`, which reads in all environment variables used to overwrite
 settings and write them to the database, so that you can safely delete them from your environment variable configuration afterwards, without
-loosing your configuration.
+losing your configuration.
 
 To run the command, execute `php bin/console settings:migrate-env-to-settings --all` as webserver user (or run `docker exec --user=www-data -it partdb php bin/console settings:migrate-env-to-settings --all` for docker containers).
 It will list you all environment variables, it found and ask you for confirmation to migrate them. Answer with `yes` to migrate them and hit enter.

docs/upgrade/index.md

@@ -6,4 +6,4 @@ has_children: true
 ---
 
 This section provides information on how to upgrade Part-DB to the latest version.
-This is intended for major release upgrades, where requirements or things changes significantly.
+This is intended for major release upgrades, where requirements or things change significantly.

docs/upgrade/upgrade_legacy.md

@@ -24,7 +24,7 @@ sections carefully before proceeding to upgrade.
   also more sensitive stuff like database migration works via CLI now, so you should have console access on your server.
 * Markdown/HTML is now used instead of BBCode for rich text in description and command fields.
   It is possible to migrate your existing BBCode to Markdown
-  via `php bin/console php bin/console partdb:migrations:convert-bbcode`.
+  via `php bin/console partdb:migrations:convert-bbcode`.
 * Server exceptions are not logged into event log anymore. For security reasons (exceptions can contain sensitive
   information) exceptions are only logged to server log (by default under './var/log'), so only the server admins can access it.
 * Profile labels are now saved in the database (before they were saved in a separate JSON file). **The profiles of legacy