Tweaks as requested

docs/home/guides/docker.md

@@ -386,29 +386,12 @@ Then run the script again:
 ```{include} wt/wt-09-next-steps.md
 ```
 
+## Other Topics
 
-### Running the container in the background:
+### Scheduling
-
-The docker commands in this article are creating and deleting containers.
-
-However, you probably ultimately want a container that runs all the time, even after reboots, and wakes up to do its thing.
-
-This would be the minimal case:
 
+```{include} wt/wt-10-scheduling.md
 ```
-docker run -d \
-  --restart=unless-stopped \
-  -v PMM_PATH_GOES_HERE:/config:rw \
-  meisnate12/plex-meta-manager
-```
-
-That will create a container that will run in the background until you explicitly stop it, surviving reboots, and waking up every morning at 5AM to process collections.
-
-There are of course [other flags you can add](../environmental), but this is the minimal command to create this container.
-
-There are [other ways you could schedule](scheduling.md) the `docker run` command used here if you don't want to use PMM's built-in scheduler and leave the container running all the time.
-
-## Other Topics
 
 ### I want to use the develop branch
 
@@ -432,7 +415,7 @@ docker run --rm -it -v "PMM_PATH_GOES_HERE:/config:rw" meisnate12/plex-meta-mana
 
 This may not work if you are not using the official image; for example, it does not work with the lsio image.
 
-### I want to ensure IO amy using the master branch
+### I want to ensure I am using the master branch
 
 Add the `latest` tag to the image name in your run command [or wherever you specify the image in your environment]
 

docs/home/guides/local.md

@@ -614,9 +614,13 @@ When you are done, deactivate the virtual environment:
 deactivate
 ```
 
-
 ## Other Topics
 
+### Scheduling
+
+```{include} wt/wt-10-scheduling.md
+```
+
 ### I want to update to the latest version of PMM
 
 ````{tab} Linux

docs/home/guides/wt/wt-10-scheduling.md

@@ -0,0 +1,13 @@
+The commands you've been using in this walkthrough runn Plex-Meta-Manager immediately.
+
+Plex Meta Manager also features multiple layers of scheduling, which you can leverage to
+
+You can run PMM in the background, telling it to wake up and process your libraries at fixed times during the day.  The default behavior in this regard is to wake up at 5AM and process the config.
+
+You can skip using that internal schedule and just do manual runs as you have been doing throughout this walkthrough using standard tools available in your OS.
+
+Details on setting this up are found [here](../scheduling.md).
+
+In addition, individual items *within* the configuration can be scheduled to take place at certain times *provided PMM is running at that time*.  For example, you can tell PMM only to apply overlays on Tuesdays or the like.  YOu can then schedule manual runs every day at noon and overlays will only get processed when it runs on Tuesday.  This sort of schedule *will not* make PMM start up if it is not already running.  If you don't arrange for PMM to be run on Tuesday, your overlays would never be processed in this example.
+
+Details on this level of scheduling are found [here](../../../metadata/details/schedule.md)

docs/home/guides/wt/wt-save.md

@@ -9,6 +9,6 @@ If you're using `nano`, type control-`x`, then `y`, then the enter key.<br/>
 ````
 ````{tab} Windows:
 <br/>
-If you're using `notepad`, type alt-`s` or choose `Save` from the `File` menu.
+If you're using `notepad`, type control-`s` or choose `Save` from the `File` menu.
 <br/>
 ````