add toc anchors to returns

proposals/009/benefits.md

@@ -16,4 +16,4 @@ Further, this allows Cyware to offer cheaper and more direct integration with a
 
 Finally, allowing a customer to choose their cloud provider and region would greatly lessen the spider-web of global compliance requirements and allow Cyware to more rapidly serve customers around the world.
 
-[<< Return](./index.md#table-of-contents)
+[<< Return](./index.md#benefits)

proposals/009/implementation.md

@@ -2,4 +2,4 @@
 
 A detailed implementation plan is beyond the scope of this document, but I wanted to include this section for completeness. If this were an actual plan, this section would detail exactly how we planned to tackle each phase of the project, from initial stakeholder discussions, the initial migration into AWS, the extension into Azure and/or GCP, milestones, resource allocations, and what will constitute "success."
 
-[<< Return](./index.md#table-of-contents)
+[<< Return](./index.md#implement)

proposals/009/index.md

@@ -10,30 +10,30 @@
 
 ## Table of Contents
 
-1. [**Introduction**](./introduction.md)
+1. [**Introduction**](./introduction.md)<a id='intro'></a>
    - [Background, Context, Assumptions](./introduction.md#background-context-assumptions)
    - [Objectives](./introduction.md#objectives)
 
-2. [**Scope of Work**](./scope.md)
+2. [**Scope of Work**](./scope.md)<a id='scope'></a>
    - [Overview of Project Scope](./scope.md#overview-of-project-scope)
    - [In-Scope Activities](./scope.md#in-scope-activities)
    - [Out-of-Scope Activities](./scope.md#out-of-scope-activities)
 
-3. [**Benefits**](./benefits.md)
+3. [**Benefits**](./benefits.md)<a id='benefits'></a>
    - [Cost Efficiency](./benefits.md#cost-efficiency)
    - [High Availability and Disaster Recovery](./benefits.md#high-availability-and-disaster-recovery)
    - [Flexibility and Vendor Neutrality](./benefits.md#flexibility-and-vendor-neutrality)
 
-4. [**Technical Details**](./techdetails.md)
+4. [**Technical Details**](./techdetails.md)<a id='tech'></a>
    - [Cloud Providers](./techdetails.md#cloud-providers)
    - [Kubernetes Distribution](./techdetails.md#kubernetes-distribution)
    - [Cluster Architecture](./techdetails.md#cluster-architecture)
    - [Networking](./techdetails.md#networking)
    - [Security](./techdetails.md#security)
 
-5. [**Implementation Plan**](./implementation.md)
+5. [**Implementation Plan**](./implementation.md)<a id='implement'></a>
 
-6. [**Risk Assessment**](./risk.md)
+6. [**Risk Assessment**](./risk.md)<a id='risk'></a>
    - [Identified Risks](./risk.md#identified-risks)
    - [Risk Mitigation Strategies](./risk.md#risk-mitigation-strategies)
 

proposals/009/introduction.md

@@ -19,4 +19,4 @@ Our Objectives Are:
 3. Upskill employees and support staff to ensure Cyware's support standards are met.
 4. Allow for multi-cloud deployment to offer customer choice, control costs, and provide flexibility in the rare event of a major cloud outage.
 
-[<< Return](./index.md#table-of-contents)
+[<< Return](./index.md#intro)

proposals/009/risk.md

@@ -8,4 +8,4 @@ In this section, we would identify risks, not only form a technical perspective,
 
 As a result of the discussions above, we should discuss and document all strategies for mitigation, or even accepting, identified risk. We should also strive to build in automated checks where possible to prevent regression as the environment organically grows.
 
-[<< Return](./index.md#table-of-contents)
+[<< Return](./index.md#risk)

proposals/009/scope.md

@@ -20,4 +20,4 @@ Without fully understanding all the intricacies of the Cyware Platform, we'll ju
 
 We won't discuss necessary but unrelated items such as securing the cloud, securing the CI/CD solution, transit or egress costs, or playbooks for how to support the solution. Although those are extremely important and would be part of an actual solution proposal, they depend on details that are unknown to me at this point. There will be high-level suggestions for several of these topics, but plans for their ultimate implementation are beyond the scope of this project.
 
-[<< Return](./index.md#table-of-contents)
+[<< Return](./index.md#scope)

proposals/009/techdetails.md

@@ -21,4 +21,4 @@ We won't get into the nuance of how to best architect cross-cloud networking, bu
 
 As with everything cloud, security will need to be carefully considered. Multi-Cloud deployments open multiple avenues of attack that are not well-known, so penetration testing, vulnerability scanning and management, as well as permissions and roles will have to be carefully considered.
 
-[<< Return](./index.md#table-of-contents)
+[<< Return](./index.md#tech)