docs: fixes following QA testing (#9690)

2024-10-22 18:20:21 +03:00
parent b2122c4073
commit 731309e87a
40 changed files with 70 additions and 66 deletions
@@ -14,7 +14,7 @@ So, resources in the module, such as services or loaders, can only resolve other

 ### List of Registered Resources

-Find a list of resources or dependencies registered in a module's container in [this Learning Resources reference](!resoures!/medusa-container-resources).
+Find a list of resources or dependencies registered in a module's container in [this Development Resources reference](!resources!/medusa-container-resources).

 ---

@@ -161,9 +161,9 @@ Refer to [MikroORM's reference](https://mikro-orm.io/api/5.9/knex/class/EntityMa

 ### Why Wrap a Transactional Method

-The variables in the transactional method (for example, `update_`) hold values that are uncomitted to the database. They're only committed once the method finishes execution.
+The variables in the transactional method (for example, `update_`) hold values that are uncommitted to the database. They're only committed once the method finishes execution.

-So, if in your method you perform database operations, then use their result to perform other actions, such as connect to a third-party service, you'll be working with uncommitted data.
+So, if in your method you perform database operations, then use their result to perform other actions, such as connecting to a third-party service, you'll be working with uncommitted data.

 By placing only the database operations in a method that has the `InjectTransactionManager` and using it in a wrapper method, the wrapper method receives the committed result of the transactional method.

@@ -201,7 +201,7 @@ In this case, only the `update_` method is wrapped in a transaction. The returne

 ### Using Methods in Transactional Methods

-If your transactional method uses other methods that accept a Medusa context, pass the shared context to those method.
+If your transactional method uses other methods that accept a Medusa context, pass the shared context to those methods.

 For example:

@@ -8,7 +8,7 @@ This chapter lists constraints to keep in mind when creating a service.

 ## Use Async Methods

-Medusa wraps service method executions to inject useful context or transactions. However, since Medusa can't detect whether the method is asynchronus, it always executes methods in the wrapper with the `await` keyword.
+Medusa wraps service method executions to inject useful context or transactions. However, since Medusa can't detect whether the method is asynchronous, it always executes methods in the wrapper with the `await` keyword.

 For example, if you have a synchronous `getMessage` method, and you use it other resources like workflows, Medusa executes it as an async method: