docs: use tooling convention across docs (#10512)

www/apps/book/app/learn/fundamentals/modules/db-operations/page.mdx

@@ -18,12 +18,12 @@ This chapter is intended for more advanced database use-cases where you need mor
 
 [MikroORM's entity manager](https://mikro-orm.io/docs/entity-manager) is a class that has methods to run queries on the database and perform operations.
 
-Medusa provides an `InjectManager` decorator imported from `@medusajs/utils` that injects a service's method with a [forked entity manager](https://mikro-orm.io/docs/identity-map#forking-entity-manager).
+Medusa provides an `InjectManager` decorator from the Modules SDK that injects a service's method with a [forked entity manager](https://mikro-orm.io/docs/identity-map#forking-entity-manager).
 
 So, to run database queries in a service:
 
 1. Add the `InjectManager` decorator to the method.
-2. Add as a last parameter an optional `sharedContext` parameter that has the `MedusaContext` decorator imported from `@medusajs/utils`. This context holds database-related context, including the manager injected by `InjectManager`
+2. Add as a last parameter an optional `sharedContext` parameter that has the `MedusaContext` decorator from the Modules SDK. This context holds database-related context, including the manager injected by `InjectManager`
 
 For example, in your service, add the following methods:
 
@@ -81,10 +81,10 @@ Refer to [MikroORM's reference](https://mikro-orm.io/api/5.9/knex/class/EntityMa
 
 To wrap database operations in a transaction, you create two methods:
 
-1. A private or protected method that's wrapped in a transaction. To wrap it in a transaction, you use the `InjectTransactionManager` decorator imported from `@medusajs/utils`.
+1. A private or protected method that's wrapped in a transaction. To wrap it in a transaction, you use the `InjectTransactionManager` decorator from the Modules SDK.
 2. A public method that calls the transactional method. You use on it the `InjectManager` decorator as explained in the previous section.
 
-Both methods must accept as a last parameter an optional `sharedContext` parameter that has the `MedusaContext` decorator imported from `@medusajs/utils`. It holds database-related contexts passed through the Medusa application.
+Both methods must accept as a last parameter an optional `sharedContext` parameter that has the `MedusaContext` decorator from the Modules SDK. It holds database-related contexts passed through the Medusa application.
 
 For example:
 

www/apps/book/app/learn/fundamentals/modules/page.mdx

@@ -28,7 +28,7 @@ Modules are created in a sub-directory of `src/modules`. So, start by creating t
 
 ### 1. Create Data Model
 
-A data model represents a table in the database. You create data models using Medusa's data modeling utility. It simplifies defining a table's columns, relations, and indexes with straightforward methods and configurations.
+A data model represents a table in the database. You create data models using Medusa's data modeling language (DML). It simplifies defining a table's columns, relations, and indexes with straightforward methods and configurations.
 
 You create a data model in a TypeScript or JavaScript file under the `models` directory of a module. So, to create a `Post` data model in the Blog Module, create the file `src/modules/blog/models/post.ts` with the following content:
 
@@ -45,7 +45,7 @@ const Post = model.define("post", {
 export default Post
 ```
 
-You define the data model using the `define` method of the `model` utility imported from `@medusajs/framework/utils`. It accepts two parameters:
+You define the data model using the `define` method of the DML. It accepts two parameters:
 
 1. The first one is the name of the data model's table in the database. Use snake-case names.
 2. The second is an object, which is the data model's schema. The schema's properties are defined using the `model`'s methods, such as `text` and `id`.
@@ -84,7 +84,7 @@ class BlogModuleService extends MedusaService({
 export default BlogModuleService
 ```
 
-Your module's service extends a class generated by the `MedusaService` utility function. This class comes with generated methods for data-management Create, Read, Update, and Delete (CRUD) operations on each of your modules, saving your time that can be spent on building custom business logic.
+Your module's service extends a class generated by `MedusaService` from the Modules SDK. This class comes with generated methods for data-management Create, Read, Update, and Delete (CRUD) operations on each of your modules, saving your time that can be spent on building custom business logic.
 
 The `MedusaService` function accepts an object of data models to generate methods for. You can pass all data models in your module in this object.
 
@@ -123,7 +123,7 @@ export default Module(BLOG_MODULE, {
 })
 ```
 
-You use the `Module` function imported from `@medusajs/framework/utils` to create the module's definition. It accepts two parameters:
+You use `Module` from the Modules SDK to create the module's definition. It accepts two parameters:
 
 1. The name that the module's main service is registered under (`blog`).
 2. An object with a required property `service` indicating the module's main service.