AWS prescriptive-guidance documentation change
Summary
Converted section titles from bold to markdown headers (###) and maintained existing content about avoiding sensitive data in tags
Security assessment
Formatting changes only. Existing security advice about sensitive data remains unchanged - no new security documentation added.
Diff
diff --git a/prescriptive-guidance/latest/tagging-best-practices/tagging-practices-to-avoid.md b/prescriptive-guidance/latest/tagging-best-practices/tagging-practices-to-avoid.md index c04cc0793..07bc787ec 100644 --- a//prescriptive-guidance/latest/tagging-best-practices/tagging-practices-to-avoid.md +++ b//prescriptive-guidance/latest/tagging-best-practices/tagging-practices-to-avoid.md @@ -19 +19 @@ Imagine a scenario where you use a tagging strategy to calculate the total costs -**Sales Forecasting** +### Sales Forecasting @@ -57 +57 @@ Examples P1 and D1 wil result in incorrect reporting or estimates for planning b -**Post-Sales Maintenance** +### Post-Sales Maintenance @@ -97 +97 @@ Tagging can be counterproductive if used with incorrect or sensitive or private -**Incorrect information in tags** +### Incorrect information in tags @@ -112 +112 @@ Having the correct tags is essential for a functional system. -**Sensitive information in tags** +### Sensitive information in tags