chore: Fix several typos (#4533)

Author: co63oc

docs/analytical_engine/deployment.md

@@ -15,7 +15,7 @@ In this document, we will walk you through the process of standalone deployment
 
 To get started, you need to install graphscope-client and prepare a Kubernetes Cluster to continue.
 
-Incase you doesn't have one, you could refer to the [Install graphscope-client](../deployment/deploy_graphscope_on_self_managed_k8s.md#install-graphscope-client) and [create kubernetes cluster](../deployment/deploy_graphscope_on_self_managed_k8s.md#prepare-a-kubernetes-cluster) to get them.
+In case you doesn't have one, you could refer to the [Install graphscope-client](../deployment/deploy_graphscope_on_self_managed_k8s.md#install-graphscope-client) and [create kubernetes cluster](../deployment/deploy_graphscope_on_self_managed_k8s.md#prepare-a-kubernetes-cluster) to get them.
 
 
 ## Deployment GAE only

docs/analytical_engine/overview_and_architecture.md

@@ -53,7 +53,7 @@ GAE also supports incremental computation over graph data via the [Ingress](http
 
 ## Application Layer
 
-GAE provides C++, Python and Java SDKs for graph applications, where users can freely choose programming models, programming languages, and computation patterns (batch computation or incremental computation) to develop their own applications. GAE of GraphScope also provides [20 graph analytics algorithms](https://graphscope.io/docs/latest/analytical_engine/builtin_algorithms.html) as built-in algorithms, and users can directly invoke them. GraphScope is compatible with NetworkX APIs, and thus diverse kinds of [built-in algorithms in NetworkX](https://networkx.org/documentation/stable/reference/algorithms/index.html) can also be directly invoked by users. In total, over 100 build-in graph analytical algorithms can be directly executed over GraphScope. Additionally, the support for the Pregel model has been implemented in GAE, and graph algorithms implemented in Giraph or GraphX can also be directly run on GAE. Please refer to the following tutorials on how to run NetworkX/Giraph/GraphX applications on GAE.
+GAE provides C++, Python and Java SDKs for graph applications, where users can freely choose programming models, programming languages, and computation patterns (batch computation or incremental computation) to develop their own applications. GAE of GraphScope also provides [20 graph analytics algorithms](https://graphscope.io/docs/latest/analytical_engine/builtin_algorithms.html) as built-in algorithms, and users can directly invoke them. GraphScope is compatible with NetworkX APIs, and thus diverse kinds of [built-in algorithms in NetworkX](https://networkx.org/documentation/stable/reference/algorithms/index.html) can also be directly invoked by users. In total, over 100 built-in graph analytical algorithms can be directly executed over GraphScope. Additionally, the support for the Pregel model has been implemented in GAE, and graph algorithms implemented in Giraph or GraphX can also be directly run on GAE. Please refer to the following tutorials on how to run NetworkX/Giraph/GraphX applications on GAE.
 
 - [Tutorial: Graph Operations with NetworkX APIs](https://graphscope.io/docs/latest/analytical_engine/tutorial_networkx_operations.html)
 - [Tutorial: Graph Algorithms with NetworkX APIs](https://graphscope.io/docs/latest/analytical_engine/tutorial_networkx_algorithms.html)

docs/deployment/persistent_storage_of_graphs_on_k8s.md

@@ -164,7 +164,7 @@ print(sub_graph.schema)
 sess.close()
 ```
 
-## Retore graphs from the pvc
+## Restore graphs from the pvc
 
 Remember the vineyard ids printed above and the pvc name and then you can restore the graphs from the pvc as follows.
 

docs/design_of_gae.md

@@ -28,7 +28,7 @@ GAE achieves high performance through a highly optimized analytical runtime base
 
 ## Algorithm Library
 
-GAE of GraphScope provides 20 graph analytics algorithms as built-in algorithms, and users can directly invoke them. The full lists of build-in algorithms are:
+GAE of GraphScope provides 20 graph analytics algorithms as built-in algorithms, and users can directly invoke them. The full lists of built-in algorithms are:
 
 - `sssp(src)`
 - `pagerank()`
@@ -52,4 +52,4 @@ GAE of GraphScope provides 20 graph analytics algorithms as built-in algorithms,
 - `sampling_path()`
 
 
-In addition, GraphScope is compatible with NetworkX APIs, and thus diverse kinds of [built-in algorithms in NetworkX](https://networkx.org/documentation/stable/reference/algorithms/index.html) can also be directly invoked by users. In total, over 100 build-in graph analytical algorithms can be directly executed over GraphScope, without any developing effort.
+In addition, GraphScope is compatible with NetworkX APIs, and thus diverse kinds of [built-in algorithms in NetworkX](https://networkx.org/documentation/stable/reference/algorithms/index.html) can also be directly invoked by users. In total, over 100 built-in graph analytical algorithms can be directly executed over GraphScope, without any developing effort.

docs/flex/coordinator/getting_started.md

@@ -1,6 +1,6 @@
 # Getting Started
 
-This guide will walk you through the process of setting up the coordinator, connecting to it via [gsctl](../../utilities/gs.md) and execuing your first command.
+This guide will walk you through the process of setting up the coordinator, connecting to it via [gsctl](../../utilities/gs.md) and executing your first command.
 
 ## Preparation
 

docs/flex/interactive/data_model.md

@@ -108,7 +108,7 @@ Temporal types can be defined in the following ways:
 ```yaml
 temporal:
   date:
-    # optional value: DF_YYYY_MM_DD, means ISO fomat: 2019-01-01
+    # optional value: DF_YYYY_MM_DD, means ISO format: 2019-01-01
     date_format: <string> 
   time:
     # optional value: TF_HH_MM_SS_SSS, means ISO format: 00:00:00.000

docs/flex/interactive/development/dev_and_test.md

@@ -215,7 +215,7 @@ The main entrance for Interactive is `interactive_server`.
 
 ### Enable AdminService
 
-To start admin service in development, use the command line argument `--enable-admin-service true`. `${ENGINE_CONFIG}` specifies the configuration for interactive query engine, see [engine-configuration](https://graphscope.io/docs/flex/interactive/configuration). `${WORKSPACE}` points to the directory where interactive related data is maintaned.
+To start admin service in development, use the command line argument `--enable-admin-service true`. `${ENGINE_CONFIG}` specifies the configuration for interactive query engine, see [engine-configuration](https://graphscope.io/docs/flex/interactive/configuration). `${WORKSPACE}` points to the directory where interactive related data is maintained.
 
 ```bash
 ./bin/interactive_server -c ${ENGINE_CONFIG} -w ${WORKSPACE} --enable-admin-service true

docs/flex/interactive/development/java/java_sdk.md

@@ -265,14 +265,14 @@ public class GettingStarted {
 }
 ```
 
-For each vertex/edge types, you need to provide the input data source and column mapping infomation.
-Remember to add `@` at the begining of the local file path. 
-`Session.bulkLoading()` will submit an dataloading job to the service, and we can query the status of the job via `Session.getJobStatus()`, and wait until the job has compleleted successfully.
+For each vertex/edge types, you need to provide the input data source and column mapping information.
+Remember to add `@` at the beginning of the local file path. 
+`Session.bulkLoading()` will submit an dataloading job to the service, and we can query the status of the job via `Session.getJobStatus()`, and wait until the job has completed successfully.
 
 ### Create a stored procedure
 
 Stored procedures can be registered into GraphScope Interactive to encapsulate and reuse complex graph operations. Interactive support both `cypher` and `c++` queries as stored procedures. 
-With the following code, you will create a procedure named `testProcedure` which is definied via a `cypher` query.
+With the following code, you will create a procedure named `testProcedure` which is defined via a `cypher` query.
 
 ```java
 public class GettingStarted{
@@ -304,7 +304,7 @@ public class GettingStarted{
 }
 ```
 
-The procedure could not be invokded now, since currently interactive service has not been switched to the newly created `test_graph`. We need to start the service on `test_graph`.
+The procedure could not be invoked now, since currently interactive service has not been switched to the newly created `test_graph`. We need to start the service on `test_graph`.
 
 ### Start the query service on the new graph
 

docs/flex/interactive/development/python/GraphManagementApi.md

@@ -101,7 +101,7 @@ Name | Type | Description  | Notes
 
 ### Return type
 
-[Reesult](./result.rst)[[**CreateGraphResponse**](CreateGraphResponse.md)]
+[Result](./result.rst)[[**CreateGraphResponse**](CreateGraphResponse.md)]
 
 
 ### Authorization

docs/flex/interactive/development/python/JobManagementApi.md

@@ -4,7 +4,7 @@ All URIs are relative to *{INTERACTIVE_ADMIN_ENDPOINT}*
 
 | Method | HTTP request | Description |
 |------------- | ------------- | -------------|
-| [**CancelJob**](JobManagementApi.md#CancelJob) | **DELETE** /v1/job/{job_id} | Cancell the job with specified jobId |
+| [**CancelJob**](JobManagementApi.md#CancelJob) | **DELETE** /v1/job/{job_id} | Cancel the job with specified jobId |
 | [**GetJobById**](JobManagementApi.md#GetJobById) | **GET** /v1/job/{job_id} | Get the metadata of the job with specified jobId |
 | [**ListJobs**](JobManagementApi.md#ListJobs) | **GET** /v1/job | List all jobs(including history jobs) |