Fix typos in docs (iree-org#6946)

Made corrections to the typos i found in the documentations.

bindings/python/iree/compiler/README.md

@@ -41,7 +41,7 @@ to further qualify the path, and there are a few placeholders that will be
 expanded:
 
 * `{id}` - A per-process monotonically increasing number for each compiler
-  invocation. Can be overriden by the API if a better symbolic name is
+  invocation. Can be overridden by the API if a better symbolic name is
   available (i.e. test case, etc).
 * `{pid}` - Process ID of the current process.
 * `{main}` - Basename of `sys.argv[0]`, which is typically the name of the

bindings/python/tests/README.md

@@ -4,5 +4,5 @@ These tests are run in an environment where all available Python bindings
 are setup on the `PYTHONPATH`. Each will internally skip itself if optional
 components are not available.
 
-Note that IREE compiler tool locations can be overriden by specifying the
+Note that IREE compiler tool locations can be overridden by specifying the
 `IREE_TOOL_PATH` environment variable.

colab/README.md

@@ -37,7 +37,7 @@ model, pre-processes it for import, then compiles it using IREE
 
 [![Open In Colab](https://colab.research.google.com/assets/colab-badge.svg)](https://colab.research.google.com/github/google/iree/blob/main/colab/tensorflow_hub_import.ipynb)
 
-### [tflite_text_classificaiton\.ipynb](tflite_text_classification.ipynb)
+### [tflite_text_classification\.ipynb](tflite_text_classification.ipynb)
 
 Downloads a pretrained
 [TFLite text classification](https://www.tensorflow.org/lite/examples/text_classification/overview)

docs/developers/design_docs/hal_driver_features.md

@@ -27,7 +27,7 @@ Vulkan has many mechanisms for supporting different hardware implementations:
 versions, extensions, features, limits. Vulkan uses SPIR-V to express the GPU
 program but Vulkan is just one client SPIR-V supports. So SPIR-V has its own
 mechanisms for supporting different clients: versions, capabilities, extensions.
-The mechanims in these two domains bear lots of similarity, but they are not
+The mechanism in these two domains bear lots of similarity, but they are not
 exactly the same. We need to bridge these two worlds inside IREE.
 
 IREE has its own [Vulkan dialect][iree-vulkan-dialect], which defines the Vulkan

docs/developers/get_started/generic_vulkan_env_setup.md

@@ -6,7 +6,7 @@ used in a wide variety of devices from PCs and consoles to mobile phones and
 embedded platforms.
 
 This page lists steps and tips for setting up and trouble shooting a Vulkan
-development envirnoment. The information here is meant to be generic.
+development environment. The information here is meant to be generic.
 
 ## Vulkan architecture
 
@@ -70,7 +70,7 @@ packages:
 
 ### Linux
 
-For other Linux distros, please consult the corresponding package managment
+For other Linux distros, please consult the corresponding package management
 tools for the packages needed. (And please feel free to update this doc
 regarding them.)
 
@@ -124,7 +124,7 @@ behavior and print verbose information, notably:
     dump of all Vulkan API calls made by the application. You can force enable
     `VK_LAYER_LUNARG_core_validation` to validate the API calls made by the
     application.
-*   `VK_LAYER_PATH`: override the loader's standard layer libary search folders.
+*   `VK_LAYER_PATH`: override the loader's standard layer library search folders.
 
 Please see the [Vulkan loader's documentation][VulkanLoaderEnvVars] for detailed
 explanation for these variables.

iree/samples/simple_embedding/README.md

@@ -9,8 +9,8 @@ supports.
 
 The main bytecode testing tool
 [iree-run-module](https://github.com/google/iree/tree/main/iree/tools/iree-run-module-main.cc)
-requires a proper operating system support to set up the runtime enviroment to
-execute an IREE bytecode module. For embeded systems, the support such as file
+requires a proper operating system support to set up the runtime environment to
+execute an IREE bytecode module. For embedded systems, the support such as file
 system or multi-thread asynchronous control may not be available. This sample
 demonstrates how to setup the simplest framework to load and run the IREE
 bytecode with various target backends.

iree/tools/android/run_module_app/README.md

@@ -45,7 +45,7 @@ In general, we need to
    1. Copy the VM FlatBuffer as `assets/module.vmfb`, write the entry function
       input buffers, and HAL driver into `assets/entry_function.txt`,
       `assets/inputs.txt`, and `assets/driver.txt`, respectively.
-   1. Copy the shared libary under `lib/<android-abi>/`.
+   1. Copy the shared library under `lib/<android-abi>/`.
    1. Compile resources under [`res/`](./res) directory into an Android DEX
       file.
    1. Package all of the above into an APK file.