Fix typos and command in docs (#134)

Author: tschiolborg

docs/available-components/brokers.md

@@ -10,7 +10,7 @@ In this section we'll list officially supported brokers.
 
 This is a special broker for local development. It uses the same functions to execute tasks,
 but all tasks are executed locally in the current thread.
-By default it uses `InMemoryResultBackend` but this can be overriden.
+By default it uses `InMemoryResultBackend` but this can be overridden.
 
 ## ZeroMQBroker
 

docs/examples/extending/result_backend.py

@@ -53,7 +53,7 @@ async def is_result_ready(
         Check if result exists.
 
         This function must check whether result
-        is available in your resul backend
+        is available in your result backend
         without fetching the result.
 
         :param task_id: id of a task.

docs/guide/architecture-overview.md

@@ -119,13 +119,13 @@ test_project
 You can specify all tasks modules to import manually.
 
 ```bash
-taskiq test_project.broker:broker test_projec.submodule.tasks test_projec.utils.tasks
+taskiq worker test_project.broker:broker test_project.submodule.tasks test_project.utils.tasks
 ```
 
 Or you can let taskiq find all python modules named tasks in current directory recursively.
 
 ```bash
-taskiq test_project.broker:broker -fsd
+taskiq worker test_project.broker:broker -fsd
 ```
 
 If you have uvloop installed, taskiq will automatically install new policies to event loop.

docs/guide/scheduling-tasks.md

@@ -22,7 +22,7 @@ Of course we can implement loop like this:
         await asyncio.sleep(timedelta(minutes=5).total_seconds)
 ```
 
-But if you have many schedules it may be a little painful to implement. So let me introuce you the `TaskiqScheduler`.
+But if you have many schedules it may be a little painful to implement. So let me introduce you the `TaskiqScheduler`.
 Let's add scheduler to our module.
 
 @[code python](../examples/schedule/intro.py)

docs/guide/state-and-deps.md

@@ -102,7 +102,7 @@ For example:
 
 @[code python](../examples/state/dependencies_tree.py)
 
-In this code, the dependency `common_dep` is going to be evaluated only once and the `dep1` and the `dep2` are going to recevie the same value. You can control this behavior by using the `use_cache=False` parameter to you dependency. This parameter will force the
+In this code, the dependency `common_dep` is going to be evaluated only once and the `dep1` and the `dep2` are going to receive the same value. You can control this behavior by using the `use_cache=False` parameter to you dependency. This parameter will force the
 dependency to reevaluate all it's subdependencies.
 
 In this example we cannot predict the result. Since the `dep2` doesn't use cache for the `common_dep` function.
@@ -167,7 +167,7 @@ If you want to do something asynchronously, convert this function to an asynchro
 
 ### Default dependencies
 
-By default taskiq has only two deendencies:
+By default taskiq has only two dependencies:
 
 - Context from `taskiq.context.Context`
 - TaskiqState from `taskiq.state.TaskiqState`

docs/guide/taskiq-with-fastapi.md

@@ -8,7 +8,7 @@ FastAPI is one of the most popular async web frameworks in python. It has gained
 1. It's easy to use;
 2. It has a cool dependency injection.
 
-In taskiq we try to make our libraries easy to use and we too have a depenndency injection. But our dependencies
+In taskiq we try to make our libraries easy to use and we too have a dependency injection. But our dependencies
 are not compatible with FastAPI's dependencies by default. That is why we have created a library "[taskiq-fastapi](https://pypi.org/project/taskiq-fastapi/)" to make integration with
 FastAPI as smooth as possible.
 

docs/guide/testing-taskiq.md

@@ -4,7 +4,7 @@ order: 9
 
 # Testing with taskiq
 
-Everytime we write programs, we want them to be correct. To achieve this, we use tests.
+Every time we write programs, we want them to be correct. To achieve this, we use tests.
 Taskiq allows you to write tests easily as if tasks were normal functions.
 
 Let's dive into examples.
@@ -76,7 +76,7 @@ After the preparations are done, we need to modify the broker's file in your pro
 
 As you can see, we added an `if` statement. If the expression is true, we replace our broker with an imemory broker.
 The main point here is to not have an actual connection during testing. It's useful because inmemory broker has
-the same interface as a real broker, but it doesn't send tasks acutally.
+the same interface as a real broker, but it doesn't send tasks actually.
 
 ## Testing tasks
 

taskiq/abc/broker.py

@@ -113,7 +113,7 @@ def add_dependency_context(self, new_ctx: Dict[Any, Any]) -> None:
         Provided dict will be used to inject new dependencies
         in all dependency graph contexts.
 
-        :param new_ctx: Additional context values for dependnecy injection.
+        :param new_ctx: Additional context values for dependency injection.
         """
         self.custom_dependency_context.update(new_ctx)
 
@@ -152,7 +152,7 @@ async def shutdown(self) -> None:
         Close the broker.
 
         This method is called,
-        when broker is closig.
+        when broker is closing.
         """
         event = TaskiqEvents.CLIENT_SHUTDOWN
         if self.is_worker_process:

taskiq/abc/middleware.py

@@ -55,7 +55,7 @@ def pre_execute(
         """
         This hook is called before executing task.
 
-        This is a worker-side hook, wich means it
+        This is a worker-side hook, which means it
         executes in the worker process.
 
         :param message: incoming parsed taskiq message.

taskiq/abc/result_backend.py

@@ -20,7 +20,7 @@ async def set_result(self, task_id: str, result: TaskiqResult[_ReturnType]) -> N
         """
         Saves result to the result backend.
 
-        Result must be save so it can be accesed later
+        Result must be save so it can be accessed later
         by the calling side of the system.
 
         :param task_id: id of a task to save.