AWS lake-formation documentation change
Summary
Fixed typo in 'functionality' spelling
Security assessment
Minor editorial correction without security impact
Diff
diff --git a/lake-formation/latest/dg/upgrade-glue-lake-formation.md index 7998ce784..db7af467a 100644 --- a/lake-formation/latest/dg/upgrade-glue-lake-formation.md +++ b/lake-formation/latest/dg/upgrade-glue-lake-formation.md @@ -11 +11 @@ AWS Lake Formation permissions enable fine-grained access control for data in yo -The Lake Formation permissions model uses coarse-grained AWS Identity and Access Management (IAM) permissions for API service access. Lake Formation uses [Data filtering and cell-level security in Lake Formation](./data-filtering.html) fctionality to restrict table access at the column, row, and cell-level for users and their applications. By comparison, the AWS Glue model grants data access via [Identity based and resource based IAM policies](https://docs.aws.amazon.com/glue/latest/dg/security_iam_service-with-iam.html#security_iam_service-with-iam-id-based-policies). +The Lake Formation permissions model uses coarse-grained AWS Identity and Access Management (IAM) permissions for API service access. Lake Formation uses [Data filtering and cell-level security in Lake Formation](./data-filtering.html) functionality to restrict table access at the column, row, and cell-level for users and their applications. By comparison, the AWS Glue model grants data access via [Identity based and resource based IAM policies](https://docs.aws.amazon.com/glue/latest/dg/security_iam_service-with-iam.html#security_iam_service-with-iam-id-based-policies).