docs: move Updates/ from subfolder to top-level tab

* better usability, especially on the narrow layout

Author: ukkopahis

docs/Basic_setup/index.md

@@ -132,7 +132,7 @@ If you prefer to automate your installations using scripts, see:
 
 If you are still running on gcgarner/IOTstack and need to migrate to SensorsIot/IOTstack, see:
 
-* [Migrating IOTstack from gcgarner to SensorsIot](Updates/gcgarner-migration.md).
+* [Migrating IOTstack from gcgarner to SensorsIot](../Updates/gcgarner-migration.md).
 
 ## recommended system patches
 

docs/Basic_setup/Updates/New-Menu-Release-Notes.md renamed to docs/Updates/New-Menu-Release-Notes.md

@@ -9,7 +9,7 @@ There are many features that are needing to be introduced into the new menu syst
 ## Breaking changes
 There are a few changes that you need to be aware of:
 
-* Docker Environmental `*.env` files are no longer a thing by default. Everything needed is specified in the service.yml file, you can still optionally use them though either with [Custom Overrides](../Custom.md) or with the [PostBuild](../../Developers/PostBuild-Script.md) script. Specific config files for certain services still work as they once did.
+* Docker Environmental `*.env` files are no longer a thing by default. Everything needed is specified in the service.yml file, you can still optionally use them though either with [Custom Overrides](../Basic_setup/Custom.md) or with the [PostBuild](../Developers/PostBuild-Script.md) script. Specific config files for certain services still work as they once did.
 * Python 3, pip3, PyYAML and Blessed are all required to be installed.
 * Not backwards compatible with old menu system. You will be able to switch back to the old menu system for a period of time by changing to the `old-menu` branch. It will be unmaintained except for critical updates. It will eventually be removed - but not before everyone is ready to leave it.
 

docs/Basic_setup/Updates/gcgarner-migration.md renamed to docs/Updates/gcgarner-migration.md

@@ -11,7 +11,7 @@ Periodically updates are made to project which include new or modified container
 5. rebuild localy created images from new Dockerfiles: `docker-compose build --pull --no-cache`
 6. update running containers to latest: `docker-compose up --build -d`
 
-*Troubleshooting:* if a container fails to restart after update
+### Troubleshooting: if a container fails to start after update
 
 * try restarting the whole stack: `docker-compose restart`
 * backup your stack settings: `cp docker-compose.yml docker-compose.yml.bak`

docs/Basic_setup/Updates/Updating-the-Project.md renamed to docs/Updates/index.md

@@ -43,9 +43,7 @@ plugins:
         Networking.md: Basic_setup/Networking.md
         RPIEasy_native.md: Basic_setup/RPIEasy_native.md
         Understanding-Containers.md: Basic_setup/Understanding-Containers.md
-        Updates/New-Menu-Release-Notes.md: Basic_setup/Updates/New-Menu-Release-Notes.md
-        Updates/Updating-the-Project.md: Basic_setup/Updates/Updating-the-Project.md
-        Updates/gcgarner-migration.md: Basic_setup/Updates/gcgarner-migration.md
+        Updates/Updating-the-Project.md: Updates/index.md
         PostBuild-Script.md: Developers/PostBuild-Script.md
         BuildStack-RandomPassword.md: Developers/BuildStack-RandomPassword.md
         BuildStack-Services.md: Developers/BuildStack-Services.md