[Minor] fix typo: catalog (#7647)

### What changes were proposed in this pull request?

Fix catalog

### Why are the changes needed?

So it correct

Fix: #N/A

### Does this PR introduce _any_ user-facing change?

None

### How was this patch tested?

N/A

Co-authored-by: Justin Mclean <[email protected]>

Author: github-actions[bot]

docs/manage-tags-in-gravitino.md

@@ -24,7 +24,7 @@ the future versions.
 :::info
 1. Metadata objects are objects that are managed in Gravitino, such as `CATALOG`, `SCHEMA`, `TABLE`,
    `COLUMN`, `FILESET`, `TOPIC`, `COLUMN`, `MODEL`, etc. A metadata object is combined by a `type` and a
-   comma-separated `name`. For example, a `CATAGLOG` object has a name "catalog1" with type
+   comma-separated `name`. For example, a `CATALOG` object has a name "catalog1" with type
    "CATALOG", a `SCHEMA` object has a name "catalog1.schema1" with type "SCHEMA", a `TABLE`
    object has a name "catalog1.schema1.table1" with type "TABLE", a `COLUMN` object has a name 
    "catalog1.schema1.table1.column1" with type "COLUMN".

docs/security/access-control.md

@@ -114,7 +114,7 @@ This process allows all users belonging to that user group to have the access co
 
 Metadata objects are managed in Gravitino, such as `CATALOG`, `SCHEMA`, `TABLE`,
 `COLUMN`, `FILESET`, `TOPIC`, `COLUMN`, `ROLE`, `METALAKE`. A metadata object is combined by a `type` and a
-comma-separated `name`. For example, a `CATAGLOG` object has a name "catalog1" with type
+comma-separated `name`. For example, a `CATALOG` object has a name "catalog1" with type
 "CATALOG", a `SCHEMA` object has a name "catalog1.schema1" with type "SCHEMA", a `TABLE`
 object has a name "catalog1.schema1.table1" with type "TABLE". A `METALAKE` object has a name "metalake1".
 

docs/trino-connector/trino-connector.md

@@ -9,7 +9,7 @@ Trino can manage and access data using the Trino connector provided by `Apache G
 After configuring the Gravitino Trino connector in Trino, Trino can automatically load catalog metadata from Gravitino, allowing users to directly access these catalogs in Trino.
 Once integrated with Gravitino, Trino can operate on all Gravitino data without requiring additional configuration. 
 The Gravitino Trino connector uses the [Trino dynamic catalog managed mechanism](https://trino.io/docs/current/admin/properties-catalog.html) to load catalogs.
-When the Gravitino Trino connector retrieves catalogs from the Gravitino server, it generates a `CREATE CATAGLOG` statement and executes
+When the Gravitino Trino connector retrieves catalogs from the Gravitino server, it generates a `CREATE CATALOG` statement and executes
 the statement on the current Trino server to register the catalogs with Trino
 
 :::note