Updated typos in multiple files

docs/guide/cli.md

@@ -818,7 +818,7 @@ management.
 -   ${HOME}/tfx/local, beam, airflow, vertex
     -   Pipeline metadata read from the configuration is stored under
         `${HOME}/tfx/${ORCHESTRATION_ENGINE}/${PIPELINE_NAME}`. This location
-        can be customized by setting environment varaible like `AIRFLOW_HOME` or
+        can be customized by setting environment variable like `AIRFLOW_HOME` or
         `KUBEFLOW_HOME`. This behavior might be changed in future releases. This
         directory is used to store pipeline information including pipeline ids
         in the Kubeflow Pipelines cluster which is needed to create runs or

docs/guide/custom_component.md

@@ -69,7 +69,7 @@ class HelloComponentSpec(types.ComponentSpec):
 
 Next, write the executor code for the new component. Basically, a new subclass
 of `base_executor.BaseExecutor` needs to be created with its `Do` function
-overriden. In the `Do` function, the arguments `input_dict`, `output_dict` and
+overridden. In the `Do` function, the arguments `input_dict`, `output_dict` and
 `exec_properties` that are passed in map to `INPUTS`, `OUTPUTS` and `PARAMETERS`
 that are defined in ComponentSpec respectively. For `exec_properties`, the value
 can be fetched directly through a dictionary lookup. For artifacts in

docs/tutorials/tfx/cloud-ai-platform-pipelines.md

@@ -769,7 +769,7 @@ gcloud config set project YOUR_PROJECT_ID
 gcloud services list --available | grep Dataflow
 
 # If you don't see dataflow.googleapis.com listed, that means you haven't been
-# granted access to enable the Dataflow API.  See your account adminstrator.
+# granted access to enable the Dataflow API.  See your account administrator.
 
 # Enable the Dataflow service: