AWS solutions documentation change
Summary
Fixed markdown formatting in route table descriptions and parameter placeholder syntax
Security assessment
Formatting changes and placeholder syntax correction without security impact.
Diff
diff --git a/solutions/latest/network-orchestration-aws-transit-gateway/using-and-customizing-route-tables.md b/solutions/latest/network-orchestration-aws-transit-gateway/using-and-customizing-route-tables.md index ae8ab9da9..d0dd8fb56 100644 --- a/solutions/latest/network-orchestration-aws-transit-gateway/using-and-customizing-route-tables.md +++ b/solutions/latest/network-orchestration-aws-transit-gateway/using-and-customizing-route-tables.md @@ -15 +15 @@ This solution creates the following default transit gateway route tables: `Flat` - * **Flat** **route table** – VPCs associated with the `Flat` policy can reach other VPCs associated with the `Flat`, `SharedServices`, or `Hybrid` policies. The `Flat` policy enables a VPC to have connectivity to many other VPCs. + * **Flat** * **route table** \- VPCs associated with the `Flat` policy can reach other VPCs associated with the `Flat`, `SharedServices`, or `Hybrid` policies. The `Flat` policy enables a VPC to have connectivity to many other VPCs. @@ -17 +17 @@ This solution creates the following default transit gateway route tables: `Flat` - * **Isolated** **route table** – VPCs associated with the `Isolated policy` can reach VPCs with the `SharedServices` and `Hybrid` policies. VPCs in the `Isolated` policy can’t use Transit Gateway to connect to other VPCs in the `Isolated` policy. This policy is for VPCs that don’t communicate with each other. + * **Isolated route table** \- VPCs associated with the `Isolated policy` can reach VPCs with the `SharedServices` and `Hybrid` policies. VPCs in the `Isolated` policy can’t use Transit Gateway to connect to other VPCs in the `Isolated` policy. This policy is for VPCs that don’t communicate with each other. @@ -19 +19 @@ This solution creates the following default transit gateway route tables: `Flat` - * **Infrastructure** **route table** – VPCs associated with the `SharedServices` policy can reach other VPCs associated with the `Isolated`, `Flat`, or `Hybrid` policies. The `SharedServices` policy is used for VPCs that many other VPCs may rely on, such as shared authentication, shared tooling, or orchestration tools. + * **Infrastructure route table** \- VPCs associated with the `SharedServices` policy can reach other VPCs associated with the `Isolated`, `Flat`, or `Hybrid` policies. The `SharedServices` policy is used for VPCs that many other VPCs may rely on, such as shared authentication, shared tooling, or orchestration tools. @@ -21 +21 @@ This solution creates the following default transit gateway route tables: `Flat` - * **On-premises route table –** This route table is used for connecting to on-premises through either [AWS Virtual Private Network](https://aws.amazon.com/vpn/) (AWS VPN) or [AWS Direct Connect](https://aws.amazon.com/directconnect/). Associate your on-premises connections to the `On-premises` route table. + * **On-premises route table -** This route table is used for connecting to on-premises through either [AWS Virtual Private Network](https://aws.amazon.com/vpn/) (AWS VPN) or [AWS Direct Connect](https://aws.amazon.com/directconnect/). Associate your on-premises connections to the `On-premises` route table. @@ -123 +123 @@ To associate a new VPC to this route table: - Attach-to-tgw: _< leave blank>_ + Attach-to-tgw: <leave blank>