AWS prescriptive-guidance documentation change
Summary
Fixed apostrophe formatting in multiple sentences
Security assessment
Typographical corrections with no impact on security content or policies
Diff
diff --git a/prescriptive-guidance/latest/cost-allocation-tagging/faq.md b/prescriptive-guidance/latest/cost-allocation-tagging/faq.md index 98033ebed..cb473bab6 100644 --- a//prescriptive-guidance/latest/cost-allocation-tagging/faq.md +++ b//prescriptive-guidance/latest/cost-allocation-tagging/faq.md @@ -19 +19 @@ Companies that are most effective in their use of tags typically create business -It’s possible to visualize cost and usage information in AWS Cost Explorer, but you will not have filters to see more granular information of cost and billing from AWS services. For example, you won’t be able to filter by application, business unit, cost center, environment, project, or product. +It's possible to visualize cost and usage information in AWS Cost Explorer, but you will not have filters to see more granular information of cost and billing from AWS services. For example, you won't be able to filter by application, business unit, cost center, environment, project, or product. @@ -34 +34 @@ There are two types of enforcement: -It’s important to define who will create and apply the tags in your company, during the creation of the tagging dictionary. Usually, application and operational tags are created by the Engineering or Architecture team. Business and financial tags are usually created by the FinOps team, and security tags are created by the Security team. +It's important to define who will create and apply the tags in your company, during the creation of the tagging dictionary. Usually, application and operational tags are created by the Engineering or Architecture team. Business and financial tags are usually created by the FinOps team, and security tags are created by the Security team.