docs: spelling, content updates for clarity (#2581)

.github/DISCUSSION_TEMPLATE/feature-request.yaml

@@ -11,7 +11,7 @@ body:
       options:
         - label: I used the GitHub search to find a similar requests and didn't find it.
           required: true
-        - label: Checked the [tasks taged](https://github.com/hay-kot/mealie/issues?q=is%3Aissue+is%3Aopen+label%3Atask+) issues and verified my feature is not covered
+        - label: Checked the [tasks tagged](https://github.com/hay-kot/mealie/issues?q=is%3Aissue+is%3Aopen+label%3Atask+) issues and verified my feature is not covered
           required: true
   - type: textarea
     id: problem

docs/docs/documentation/getting-started/api-usage.md

@@ -142,5 +142,5 @@ And this `orderDirection` value: <br>
 
 This will result in a recipe query where all recipes are sorted by `lastMade` ascending, then `createdAt` descending, and finally `slug` descending.
 
-Similar to query filters, when querying tables with relationships, you can order by properties on related tables. For instance, if you want to query all foods with labels, sorted by label name, you could use this `orderBy`: <br>
+Similar to query filters, when querying tables with relationships, you can order by properties on related tables. For instance, if you want to query all foods with labels, sorted by label name, you could use this `orderBy` value: <br>
 `label.name`

docs/docs/documentation/getting-started/installation/installation-checklist.md

@@ -28,14 +28,14 @@ To deploy mealie on your local network it is highly recommended to use docker to
 
 ## Migrating From over V1 Versions
 
-We've gone through a few versions of Mealie v1 deployment targets. We have settled on a single container deployment and we've begun publishing the nightly container on github containers. If you're looking to move from the old nighlty, to the new nightly there are a few things you need to do.
+We've gone through a few versions of Mealie v1 deployment targets. We have settled on a single container deployment and we've begun publishing the nightly container on github containers. If you're looking to move from the old nightly (split containers *or* the omni image) to the new nightly, there are a few things you need to do:
 
 1. Take a backup just in case!
 2. Replace the image for the API container with `ghcr.io/mealie-recipes/mealie:nightly`
 3. Take the external port from the frontend container and set that as the port mapped to port `9000` on the new container. The frontend is now served on port 9000 from the new container, so it will need to be mapped for you to have access.
 4. Restart the container
 
-The container swap should be seemless, atleast that's our hope!
+For an example of what these changes look like, see the new [SQLite](./sqlite.md) or [PostgreSQL](./postgres.md) docker-compose examples. The container swap should be seemless, at least that's our hope!
 
 ## Step 1: Deployment Type
 SQLite is a popular, open source, self-contained, zero-configuration database that is the ideal choice for Mealie when you have 1-20 Users and your concurrent write operations will be some-what limited.
@@ -46,7 +46,6 @@ You can find the relevant ready to use docker-compose files for supported instal
 
 - [SQLite](./sqlite.md)
 - [PostgreSQL](./postgres.md)
-- [Single container](./single-container.md)
 
 ## Step 2: Setting up your files.
 
@@ -77,6 +76,10 @@ $ docker-compose up -d
 
 You should see the containers start up without error. You should now be able to access the Mealie frontend at [http://localhost:9925](http://localhost:9925).
 
+!!! warning "Default Username"
+
+    Note that the default username (below) has been changed from previous versions
+
 !!! tip "Default Credentials"
 
     **Username:** changeme@example.com

docs/docs/documentation/getting-started/installation/postgres.md

@@ -60,5 +60,5 @@ volumes:
 
 <!-- Updating This? Be Sure to also update the SQLite Annotations -->
 
-1.  To access the mealie interface you only need to expose port 9000 on the mealie-frontend container. Here we expose port 9925 on the host, feel free to change this to any port you like.
+1.  To access the mealie interface you only need to expose port 9000 on the mealie container. Here we expose port 9925 on the host, but feel free to change this to any port you like.
 2.  Setting an explicit memory limit is recommended. Python can pre-allocate larger amounts of memory than is necessary if you have a machine with a lot of RAM. This can cause the container to idle at a high memory usage. Setting a memory limit will improve idle performance.

docs/docs/documentation/getting-started/installation/sqlite.md

@@ -10,11 +10,11 @@ SQLite is a popular, open source, self-contained, zero-configuration database th
 ---
 version: "3.7"
 services:
-  mealie-api:
+  mealie:
     image: ghcr.io/mealie-recipes/mealie:nightly
-    container_name: mealie-api
+    container_name: mealie
     ports:
-        "9925:9000" # (1)
+        - "9925:9000" # (1)
     deploy:
       resources:
         limits:
@@ -39,5 +39,5 @@ volumes:
 
 <!-- Updating This? Be Sure to also update the Postgres Annotations -->
 
-1.  To access the mealie interface you only need to expose port 9000 on the mealie-frontend container. Here we expose port 9925 on the host, feel free to change this to any port you like.
+1.  To access the mealie interface you only need to expose port 9000 on the container. Here we expose port 9925 on the host, but feel free to change this to any port you like.
 2.  Setting an explicit memory limit is recommended. Python can pre-allocate larger amounts of memory than is necessary if you have a machine with a lot of RAM. This can cause the container to idle at a high memory usage. Setting a memory limit will improve idle performance.