continuing to tidy up broken links

website/docs/archive/hubs-cloud/hubs-cloud-aws/aws-troubleshooting.md

@@ -146,7 +146,7 @@ Your account is likely **NOT** an admin! Switch account or check your hub stack
 
 ### How can I tell I'm on version 1.1.0?
 
-Follow steps in [Check if you're on version 1.1.0](./updating-the-stack.md#check-if-youre-on-version-110)
+Follow steps in [Check if you're on version 1.1.0](./updating-the-stack.md)
 
 ## Missing a solution?
 

website/docs/archive/hubs-cloud/hubs-cloud-aws/backup-and-restore.md

@@ -8,7 +8,7 @@ If something goes wrong and you need to restore from a backup, or you'd like to
 
 Your hub's data is made up of two things: an AWS Aurora Serverless database, and an AWS Elastic File Store volume (used for scenes, avatars, etc.) Both of these are backed up for you automatically on a nightly basis. The database is backed up via database snapshots (which can be seen in the RDS console) and the EFS volume is backed up into a Vault in AWS Backup (which can be found in the AWS Backup console.)
 
-**Do you need to update your Hubs Cloud stack from 1.0.0 to 1.1.0?** Follow the guide: [update from Hubs Cloud version 1.0.0 to 1.1.0](./updating-the-stack.md#upgrade-to-a-new-stack-release)
+**Do you need to update your Hubs Cloud stack from 1.0.0 to 1.1.0?** Follow the guide: [update from Hubs Cloud version 1.0.0 to 1.1.0](./updating-the-stack.md)
 
 ### Creating a backup manually
 

website/docs/archive/hubs-cloud/hubs-cloud-aws/cost-saving.md

@@ -24,7 +24,7 @@ See our [Estimating Costs and Charts (Alpha)](./estimating-cost.md) page.
 
 We've done our best to minimize costs in the template as much as possible. Your primary costs will be the EC2 AWS Server types you use hourly, the serverless hourly database costs, EFS storage, and, if you do not switch to Cloudflare, data transfer costs.
 
-EC2 instances, while "Online", will cost the [minimum cost](./estimating-cost.md) per hour per server for your instance AWS server type [(?)](./estimating-cost.md#aws-server-type-recommendations). This minimum cost is hourly regardless of how many people connect at a time. You can manually turn off your EC2 instance + database via turning on [**Offline mode**](./cost-saving.md#offline-mode---manual) where no one can connect to your server at the time.
+EC2 instances, while "Online", will cost the [minimum cost](./estimating-cost.md) per hour per server for your instance AWS server type [(?)](./estimating-cost.md). This minimum cost is hourly regardless of how many people connect at a time. You can manually turn off your EC2 instance + database via turning on [**Offline mode**](./cost-saving.md#offline-mode---manual) where no one can connect to your server at the time.
 
 Database costs is the largest factor next to EC2 instance, you can set [**database pausing**](./cost-saving.md#database-pausing---automatic) on to stop costs incurring when no one is connected.
 
@@ -74,15 +74,15 @@ For development with only a few users connecting + setting rooms + scenes, we re
 
 If your instance is in [**Offline mode**](./cost-saving.md#offline-mode---manual), manually update the stack to **Online** and wait 10 minutes.
 
-After, at least 1 hour before event, manually update the stack to scale up your AWS Server Type. For example 1 hour before your event, [update the stack](./updating-the-stack.md) from a **t3.medium** to **c4.large** [(?)](./estimating-cost.md#aws-server-type-recommendations).
+After, at least 1 hour before event, manually update the stack to scale up your AWS Server Type. For example 1 hour before your event, [update the stack](./updating-the-stack.md) from a **t3.medium** to **c4.large** [(?)](./estimating-cost.md).
 
 ### During your event
 
-If you notice performance issues, you can ad hoc [update the stack](./updating-the-stack.md) up more from a **c4.large** to **c5.2xlarge** [(?)](./estimating-cost.md#aws-server-type-recommendations). Your users in the rooms will have a brief freeze/voice drop while the users roll to the new servers.
+If you notice performance issues, you can ad hoc [update the stack](./updating-the-stack.md) up more from a **c4.large** to **c5.2xlarge** [(?)](./estimating-cost.md). Your users in the rooms will have a brief freeze/voice drop while the users roll to the new servers.
 
 ### After your event
 
-Scale down your AWS Server Type by [updating the stack](./updating-the-stack.md) from the **c5.2xlarge** to **t3.medium** [(?)](./estimating-cost.md#aws-server-type-recommendations) when finished or there are less users connected.
+Scale down your AWS Server Type by [updating the stack](./updating-the-stack.md) from the **c5.2xlarge** to **t3.medium** [(?)](./estimating-cost.md) when finished or there are less users connected.
 
 ### When no one is connecting to your instance for a long time
 

website/docs/archive/hubs-cloud/hubs-cloud-aws/estimating-cost.md

@@ -159,7 +159,7 @@ To see how vCPU to CCU Min/Max was estimated see [AWS Estimated CCU Limits](./es
 
 2 app x 2 streaming servers recommended for best performance. [Why?](./estimating-cost.md#why-enterprise-2-app-x-2-stream)
 
-[How to read and use Alpha Cost Charts](./estimating-cost.md#how-to-read-and-use-alpha-cost-charts)
+[How to read and use Alpha Cost Charts](./estimating-cost.md)
 
 | EC2 Server Type                | Total vCPU (#) | Min CCU | Max CCU | Cost for EC2 (US\$/hr) |
 | ------------------------------ | -------------- | ------- | ------- | ---------------------- |