AWS mwaa documentation change
Summary
Changed 'see' to 'refer to' in two documentation links (stylistic wording change)
Security assessment
The changes are purely editorial/grammatical with no impact on security content or functionality. No security implications are present in the wording adjustment.
Diff
diff --git a/mwaa/latest/migrationguide/key-considerations.md b/mwaa/latest/migrationguide/key-considerations.md index 77f89df57..90fcc6709 100644 --- a//mwaa/latest/migrationguide/key-considerations.md +++ b//mwaa/latest/migrationguide/key-considerations.md @@ -24 +24 @@ Amazon MWAA uses AWS Identity and Access Management (IAM) to control access to t -You can further manage and restrict Apache Airflow users to access only a subset of your workflow DAGs by creating custom Airflow roles and mapping them to your IAM principals. For more information and a step-by-step tutorial, see [Tutorial: Restricting an Amazon MWAA user's access to a subset of DAGs](https://docs.aws.amazon.com/mwaa/latest/userguide/limit-access-to-dags.html). +You can further manage and restrict Apache Airflow users to access only a subset of your workflow DAGs by creating custom Airflow roles and mapping them to your IAM principals. For more information and a step-by-step tutorial, refer to [Tutorial: Restricting an Amazon MWAA user's access to a subset of DAGs](https://docs.aws.amazon.com/mwaa/latest/userguide/limit-access-to-dags.html). @@ -26 +26 @@ You can further manage and restrict Apache Airflow users to access only a subset -You can also configure federated identities to access Amazon MWAA. For more information see the following. +You can also configure federated identities to access Amazon MWAA. For more information refer to the following.