AWS lake-formation documentation change
Summary
Fixed grammatical error ('opt' → 'opts') and article casing in hybrid access mode documentation
Security assessment
Minor language clarification without altering security processes or controls. No security implications detected.
Diff
diff --git a/lake-formation/latest/dg/hybrid-access-workflow.md b/lake-formation/latest/dg/hybrid-access-workflow.md index e78a01722..a107abbfe 100644 --- a//lake-formation/latest/dg/hybrid-access-workflow.md +++ b//lake-formation/latest/dg/hybrid-access-workflow.md @@ -11 +11 @@ The following diagram shows how Lake Formation authorization works in hybrid acc -Before accessing data in your data lake, a data lake administrator or a user with administrative permissions sets up individual Data Catalog table user policies to allow or deny access to tables in your Data Catalog. Then, a principal who has the permissions to perform `RegisterResource` operation registers the Amazon S3 location of the table with Lake Formation in hybrid access mode. If a data location is not registered with Lake Formation, The administrator grants Lake Formation permissions to specific users on the Data Catalog databases and tables and opt them in to use Lake Formation permissions for those databases and tables in hybrid access mode. +Before accessing data in your data lake, a data lake administrator or a user with administrative permissions sets up individual Data Catalog table user policies to allow or deny access to tables in your Data Catalog. Then, a principal who has the permissions to perform `RegisterResource` operation registers the Amazon S3 location of the table with Lake Formation in hybrid access mode. If a data location is not registered with Lake Formation, the administrator grants Lake Formation permissions to specific users on the Data Catalog databases and tables and opts them in to use Lake Formation permissions for those databases and tables in hybrid access mode.