Fix typos in docs (#6946)
Made corrections to the typos i found in the documentations.
diff --git a/bindings/python/iree/compiler/README.md b/bindings/python/iree/compiler/README.md
index f6ad6f6..bd19d0b 100644
--- a/bindings/python/iree/compiler/README.md
+++ b/bindings/python/iree/compiler/README.md
@@ -41,7 +41,7 @@
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
diff --git a/bindings/python/tests/README.md b/bindings/python/tests/README.md
index a0a288e..e6e6c29 100644
--- a/bindings/python/tests/README.md
+++ b/bindings/python/tests/README.md
@@ -4,5 +4,5 @@
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.
diff --git a/colab/README.md b/colab/README.md
index 7868737..34bbc76 100644
--- a/colab/README.md
+++ b/colab/README.md
@@ -37,7 +37,7 @@
[](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)
diff --git a/docs/developers/design_docs/hal_driver_features.md b/docs/developers/design_docs/hal_driver_features.md
index da9a125..7ef7cbb 100644
--- a/docs/developers/design_docs/hal_driver_features.md
+++ b/docs/developers/design_docs/hal_driver_features.md
@@ -27,7 +27,7 @@
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
diff --git a/docs/developers/get_started/generic_vulkan_env_setup.md b/docs/developers/get_started/generic_vulkan_env_setup.md
index 43fe77d..13a68dd 100644
--- a/docs/developers/get_started/generic_vulkan_env_setup.md
+++ b/docs/developers/get_started/generic_vulkan_env_setup.md
@@ -6,7 +6,7 @@
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 @@
### 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 @@
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.
diff --git a/iree/samples/simple_embedding/README.md b/iree/samples/simple_embedding/README.md
index da1ce0e..bcfd7b3 100644
--- a/iree/samples/simple_embedding/README.md
+++ b/iree/samples/simple_embedding/README.md
@@ -9,8 +9,8 @@
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.
diff --git a/iree/tools/android/run_module_app/README.md b/iree/tools/android/run_module_app/README.md
index afba41d..6bca552 100644
--- a/iree/tools/android/run_module_app/README.md
+++ b/iree/tools/android/run_module_app/README.md
@@ -45,7 +45,7 @@
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.
