AWS solutions documentation change
Summary
Formatting changes: Replaced en-dash with escaped hyphen in list items
Security assessment
Changes are purely formatting adjustments (punctuation markdown syntax) with no security implications
Diff
diff --git a/solutions/latest/network-orchestration-aws-transit-gateway/aws-accounts-for-multi-account-environments.md b/solutions/latest/network-orchestration-aws-transit-gateway/aws-accounts-for-multi-account-environments.md index fbfc53673..a0bd7bdab 100644 --- a/solutions/latest/network-orchestration-aws-transit-gateway/aws-accounts-for-multi-account-environments.md +++ b/solutions/latest/network-orchestration-aws-transit-gateway/aws-accounts-for-multi-account-environments.md @@ -9 +9 @@ To deploy a multi-account environment, we recommend the following AWS account gu - * **Hub stack** – Deploy to a member account in your AWS Organization, preferably where you have an existing transit gateway or plan to create a new one, or in a dedicated [network account](./concepts-and-definitions.html) where you plan to create a new transit gateway. It can’t be the Organizations management account. + * **Hub stack** \- Deploy to a member account in your AWS Organization, preferably where you have an existing transit gateway or plan to create a new one, or in a dedicated [network account](./concepts-and-definitions.html) where you plan to create a new transit gateway. It can’t be the Organizations management account. @@ -11 +11 @@ To deploy a multi-account environment, we recommend the following AWS account gu - * **Spoke stack** – Deploy to all the member accounts in your AWS Organization that have a VPC that you plan to attach to the transit gateway hub account. You must deploy it in the hub account if you want to attach VPCs in the hub account. + * **Spoke stack** \- Deploy to all the member accounts in your AWS Organization that have a VPC that you plan to attach to the transit gateway hub account. You must deploy it in the hub account if you want to attach VPCs in the hub account. @@ -13 +13 @@ To deploy a multi-account environment, we recommend the following AWS account gu - * **Organization role stack** – Optionally deploy in the Organizations management account to allow the solution to add Organizational Unit paths in the attachment name to help you identify the VPC location. + * **Organization role stack** \- Optionally deploy in the Organizations management account to allow the solution to add Organizational Unit paths in the attachment name to help you identify the VPC location.