chore: fix some typos in comment

Signed-off-by: cuibuwei <cuibuwei@gmail.com>

saved/user-interfaces/general/overview.md

@@ -64,7 +64,7 @@ The properties of these categories are displayed in the same way as the glossari
 
 ![category](egeria-ui-glossary-categories.png)
 
-Clicking a cateogry row in this table will show the terms associated with its respective category. Each term in this case describes a concept or phrase used in the data model, and clicking on one of these terms rows will redirect to the same `asset details` page as from the asset catalog.
+Clicking a category row in this table will show the terms associated with its respective category. Each term in this case describes a concept or phrase used in the data model, and clicking on one of these terms rows will redirect to the same `asset details` page as from the asset catalog.
 
 ![terms](egeria-ui-glossary-terms.png)
 

site/docs/education/egeria-dojo/running-egeria/configuring-and-operating-a-server.md

@@ -338,7 +338,7 @@ For this exercise, you will be using the following Postman collections:
 The aim is to show the differences between the fine-grained repository services APIs and the 
 course-grained, but more specialized, access services APIs.
 
-Start with the the Asset Owner OMAS interface and add a CSV file.  This returns a list of assets it has created,
+Start with the Asset Owner OMAS interface and add a CSV file.  This returns a list of assets it has created,
 one for the directory and one for the filename.  Retrieve these assets using the repository service API to see how these assets are stored.
 
 What are the differences?

site/docs/features/anchor-management/overview.md

@@ -44,7 +44,7 @@ If a [GlossaryTerm](/practices/common-data-definitions/anatomy-of-a-glossary), o
     because they are not anchored to the Asset.
     Also notice there are two NoteLogs attached to the asset,
     one with the Anchors classification and one without.
-    The one with the Anchors classification is anchored to the the Asset. The one without the Anchors classification is
+    The one with the Anchors classification is anchored to the Asset. The one without the Anchors classification is
     independent of the Asset.
 
     ![Figure 2](/features/anchor-management/anchors-classifications-on-attached-objects.svg)

site/docs/getting-started/dojo/egeria-dojo-day-1-3-2-2-calling-server-api.md

@@ -18,7 +18,7 @@ courser-grained, but more specialized access services APIs.
 
 ![Design philosophy](/guides/developer/design-philosophy-omas-omrs.png)
 
-Start with the the Asset Owner OMAS interface and add a CSV file.  This returns a list of assets it has created,
+Start with the Asset Owner OMAS interface and add a CSV file.  This returns a list of assets it has created,
 one for the directory and one for the filename.  Retrieve these assets using the 
 
 Now use the repository service API to see how these assets are stored.

site/snippets/admin/configuring-the-local-repository.md

@@ -34,7 +34,7 @@ Egeria provides a number of implementations of such a repository -- only one of
         The request body is a map of property names to values that are passed directly to XTDB when the sever starts up.
 
         ??? info "For Egeria releases before version 5.0 ...
-            The XTDB connector is located in its own git repository [egeria-connector-xtdb.git](https://github.com/odpi/egeria-connector-xtdb).  The JAR file needs to be built from this repository and placed the OMAG Server Platform's class path.  It is configured in the Metadata Access Store using the follwoing command: 
+            The XTDB connector is located in its own git repository [egeria-connector-xtdb.git](https://github.com/odpi/egeria-connector-xtdb).  The JAR file needs to be built from this repository and placed the OMAG Server Platform's class path.  It is configured in the Metadata Access Store using the following command: 
             ```
             POST {{platformURLRoot}}/open-metadata/admin-services/users/{{adminUserId}}/servers/{{serverName}}/local-repository/mode/plugin-repository/connection
             ```
@@ -62,7 +62,7 @@ Egeria provides a number of implementations of such a repository -- only one of
         POST {{platformURLRoot}}/open-metadata/admin-services/users/{{adminUserId}}/servers/{{serverName}}/local-repository/mode/local-graph-repository
         ```
 
-    If no request body is used, metadata will be stored on the local disk.  It is possible to pass a set of storage properties to JanusGraph to enalbe it to use a different persistance service.  However, the repository uses local transactions and is does not support multiple instances of the same server/repository to be active at one time. 
+    If no request body is used, metadata will be stored on the local disk.  It is possible to pass a set of storage properties to JanusGraph to enable it to use a different persistence service.  However, the repository uses local transactions and is does not support multiple instances of the same server/repository to be active at one time. 
 
 === "in-memory"