diff --git a/docs/tutorials/build-first-react.md b/docs/tutorials/build-first-react.md
index 12cf1a0fb7..73dba13862 100644
--- a/docs/tutorials/build-first-react.md
+++ b/docs/tutorials/build-first-react.md
@@ -35,7 +35,7 @@ Once the react app is running and you have your catalog dependency, the next ste
 
 :::tip
 
-For the `REACT_APP_NODE_URI` you can connect to a [QuickNode](https://www.quicknode.com/) or [Infura](https://infura.io/) puclic Node. Both services allow to connect your dApp to different blockchain networks. You will need to connect to interact with Nevermined contracts.
+For the `REACT_APP_NODE_URI` you can connect to a [QuickNode](https://www.quicknode.com/) or [Infura](https://infura.io/) public Node. Both services allow to connect your dApp to different blockchain networks. You will need to connect to interact with Nevermined contracts.
 
 :::
 
@@ -100,7 +100,7 @@ root.render(
 reportWebVitals();
 ```
 
-4. After that you will be able to iteract with the Nevermined ecosystem. List did assets deployed updating your `App.tsx`
+4. After that you will be able to interact with the Nevermined ecosystem. List did assets deployed updating your `App.tsx`
 
 ```tsx
 import { AssetService } from '@nevermined-io/catalog'
diff --git a/docs/tutorials/connect-cli.md b/docs/tutorials/connect-cli.md
index 0746d21e32..d9517f5a5c 100644
--- a/docs/tutorials/connect-cli.md
+++ b/docs/tutorials/connect-cli.md
@@ -117,7 +117,7 @@ Let's define first what is our use case:
 
 :::note Use Case
 
-As a content creator I want to tokenize a fractal I created. I want to make available **10 editions** of it, and sell them for **100 USDC** each of them. Whoever owning one of these editions will be able to have **exclusive access** to the fractal file.
+As a content creator I want to tokenize a fractal I created. I want to make available **10 editions** of it, and sell them for **100 USDC** each of them. Whoever owns one of these editions will be able to have **exclusive access** to the fractal file.
 
 :::
 
diff --git a/docs/tutorials/login-wallet-provider.md b/docs/tutorials/login-wallet-provider.md
index 1d57fbd7d5..f88164b7c6 100644
--- a/docs/tutorials/login-wallet-provider.md
+++ b/docs/tutorials/login-wallet-provider.md
@@ -13,11 +13,11 @@ In this tutorial you will learn how you can integrate Wallet Provider from the C
 ## Requirements
 For the tutorial you will need:
 
-- A extension of [Metamask](https://metamask.io/) installed in the browser
+- An extension of [Metamask](https://metamask.io/) installed in the browser
 - [node](https://nodejs.org/en/) and [npm](https://docs.npmjs.com/downloading-and-installing-node-js-and-npm) need to be installed
 
 ## How to install Catalog Provider
-Firstable to install [Catalog Provider](../react-components/providers/README.md) you just need to run:
+First to install [Catalog Provider](../react-components/providers/README.md) you just need to run:
 
 <Tabs>
   <TabItem label="yarn" value="yarn" default>
@@ -97,7 +97,7 @@ In this component we have the `login` and `logout` functions and the `walletAddr
 How you can see, we also have `getConnectors` which includes all the providers available to connect.
 
 ## Config your network (optional)
-At least that you need to set differents networks for your dapp than [polygon](https://polygon.technology/) chains config is not needed, anyway here we show you how should look the config object.
+At least that you need to set different networks for your dapp than [polygon](https://polygon.technology/) chains config is not needed, anyway here we show you how should look the config object.
 
 ```ts
 const ChainsConfig: Chain[] = [
@@ -198,4 +198,4 @@ ReactDOM.render(
 
 ## Demo
 
-<ProvidersApp/>
\ No newline at end of file
+<ProvidersApp/>
diff --git a/docs/tutorials/query-assets-catalog.md b/docs/tutorials/query-assets-catalog.md
index 239f1196fd..12ec16fc1f 100644
--- a/docs/tutorials/query-assets-catalog.md
+++ b/docs/tutorials/query-assets-catalog.md
@@ -84,7 +84,7 @@ const QuerySearchByName = (): => {
 </BrowserOnly>
 
 ## Search by additional information
-The [Additional Information](../architecture/specs/Spec-METADATA.md#additional-attributes) section is an entry into the DDO/Metadata document where users can specify a free range of attributes. They can be domain specific, and the marketplace can be used to search accross them. Things like `categories`:
+The [Additional Information](../architecture/specs/Spec-METADATA.md#additional-attributes) section is an entry into the DDO/Metadata document where users can specify a free range of attributes. They can be domain specific, and the marketplace can be used to search across them. Things like `categories`:
 
 ### Code
 
@@ -496,4 +496,4 @@ const QuerySearchSortByPrice = () => {
 
 <BrowserOnly fallback={<div>Loading search assets sorting in big objects...</div>}>
  {()=> <QueryAssets complexSort={true}/>}
-</BrowserOnly>
\ No newline at end of file
+</BrowserOnly>