Merge pull request #297 from lewagon/gcp-wsl-typo

Typo resource io ressource

LINUX.md

@@ -912,11 +912,11 @@ Now that you have created a `GCP account` and a `project` (identified by its `PR
   <summary>🤔 Why do we need a service account key ?</summary>
 
 
-  You have created a `GCP account` linked to your credit card. Your account will be billed according to your usage of the ressources of the **Google Cloud Platform**. The billing will occur if you consume anything once the free trial is over, or if you exceed the amount of spending allowed during the free trial.
+  You have created a `GCP account` linked to your credit card. Your account will be billed according to your usage of the resources of the **Google Cloud Platform**. The billing will occur if you consume anything once the free trial is over, or if you exceed the amount of spending allowed during the free trial.
 
-  In your `GCP account`, you have created a single `GCP project`, identified by its `PROJECT_ID`. The `GCP projects` allow you to organize and monitor more precisely how you consume the **GCP** ressources. For the purpose of the bootcamp, we are only going to create a single project.
+  In your `GCP account`, you have created a single `GCP project`, identified by its `PROJECT_ID`. The `GCP projects` allow you to organize and monitor more precisely how you consume the **GCP** resources. For the purpose of the bootcamp, we are only going to create a single project.
 
-  Now, we need a way to tell which ressources within a `GCP project` our code will be allowed to consume. Our code consumes GCP ressources through API calls.
+  Now, we need a way to tell which resources within a `GCP project` our code will be allowed to consume. Our code consumes GCP resources through API calls.
 
   Since API calls are not free, it is important to define with caution how our code will be allowed to use them. During the bootcamp this will not be an issue and we are going to allow our code to use all the API of **GCP** without any restrictions.
 
@@ -937,7 +937,7 @@ Since the [service account](https://cloud.google.com/iam/docs/service-accounts)
   - Click on **CREATE SERVICE ACCOUNT**:
   - Give a `Service account name` to that account
   - Click on **CREATE AND CONTINUE**
-  - Click on **Select a role** and choose `Quick access/Basic` then **Owner**, which gives full access to all ressources
+  - Click on **Select a role** and choose `Quick access/Basic` then **Owner**, which gives full access to all resources
   - Click on **CONTINUE**
   - Click on **DONE**
 - Download the service account json file 🔑:

LINUX_keep_current.md

@@ -229,7 +229,7 @@ Make sure that the file contains the correct :
 
 👉 If this does not display anything or if the email inside of the file is not the one of your service account, go back to the setup
 
-Make sure that Docker recognizes the GCP ressources :
+Make sure that Docker recognizes the GCP resources :
 
 ``` bash
 gcloud auth configure-docker

WINDOWS.md

@@ -1564,11 +1564,11 @@ Now that you have created a `GCP account` and a `project` (identified by its `PR
   <summary>🤔 Why do we need a service account key ?</summary>
 
 
-  You have created a `GCP account` linked to your credit card. Your account will be billed according to your usage of the ressources of the **Google Cloud Platform**. The billing will occur if you consume anything once the free trial is over, or if you exceed the amount of spending allowed during the free trial.
+  You have created a `GCP account` linked to your credit card. Your account will be billed according to your usage of the resources of the **Google Cloud Platform**. The billing will occur if you consume anything once the free trial is over, or if you exceed the amount of spending allowed during the free trial.
 
-  In your `GCP account`, you have created a single `GCP project`, identified by its `PROJECT_ID`. The `GCP projects` allow you to organize and monitor more precisely how you consume the **GCP** ressources. For the purpose of the bootcamp, we are only going to create a single project.
+  In your `GCP account`, you have created a single `GCP project`, identified by its `PROJECT_ID`. The `GCP projects` allow you to organize and monitor more precisely how you consume the **GCP** resources. For the purpose of the bootcamp, we are only going to create a single project.
 
-  Now, we need a way to tell which ressources within a `GCP project` our code will be allowed to consume. Our code consumes GCP ressources through API calls.
+  Now, we need a way to tell which resources within a `GCP project` our code will be allowed to consume. Our code consumes GCP resources through API calls.
 
   Since API calls are not free, it is important to define with caution how our code will be allowed to use them. During the bootcamp this will not be an issue and we are going to allow our code to use all the API of **GCP** without any restrictions.
 
@@ -1589,7 +1589,7 @@ Since the [service account](https://cloud.google.com/iam/docs/service-accounts)
   - Click on **CREATE SERVICE ACCOUNT**:
   - Give a `Service account name` to that account
   - Click on **CREATE AND CONTINUE**
-  - Click on **Select a role** and choose `Quick access/Basic` then **Owner**, which gives full access to all ressources
+  - Click on **Select a role** and choose `Quick access/Basic` then **Owner**, which gives full access to all resources
   - Click on **CONTINUE**
   - Click on **DONE**
 - Download the service account json file 🔑:
@@ -1603,7 +1603,7 @@ Since the [service account](https://cloud.google.com/iam/docs/service-accounts)
 The browser has now saved the service account json file 🔑 in your downloads directory (it is named according to your service account name, something like `le-wagon-data-123456789abc.json`)
 
 
-We will now move the service account json file from your Windows disk to the Ubuntu disk. This will allow the development tools in Ubuntu to access to the ressources of your GCP account.
+We will now move the service account json file from your Windows disk to the Ubuntu disk. This will allow the development tools in Ubuntu to access to the resources of your GCP account.
 
 First, let's create a directory in which we will store the file.
 
@@ -1681,6 +1681,7 @@ code ~/.zshrc
 in the Terminal! 😄
 
 
+
 <details>
   <summary>ℹ️ How to find the absolute path of a file?</summary>
   You can drag and drop the file in your terminal.

WINDOWS_keep_current.md

@@ -229,7 +229,7 @@ Make sure that the file contains the correct :
 
 👉 If this does not display anything or if the email inside of the file is not the one of your service account, go back to the setup
 
-Make sure that Docker recognizes the GCP ressources :
+Make sure that Docker recognizes the GCP resources :
 
 ``` bash
 gcloud auth configure-docker

_partials/gcp_setup.md

@@ -164,11 +164,11 @@ Now that you have created a `GCP account` and a `project` (identified by its `PR
   <summary>🤔 Why do we need a service account key ?</summary>
 
 
-  You have created a `GCP account` linked to your credit card. Your account will be billed according to your usage of the ressources of the **Google Cloud Platform**. The billing will occur if you consume anything once the free trial is over, or if you exceed the amount of spending allowed during the free trial.
+  You have created a `GCP account` linked to your credit card. Your account will be billed according to your usage of the resources of the **Google Cloud Platform**. The billing will occur if you consume anything once the free trial is over, or if you exceed the amount of spending allowed during the free trial.
 
-  In your `GCP account`, you have created a single `GCP project`, identified by its `PROJECT_ID`. The `GCP projects` allow you to organize and monitor more precisely how you consume the **GCP** ressources. For the purpose of the bootcamp, we are only going to create a single project.
+  In your `GCP account`, you have created a single `GCP project`, identified by its `PROJECT_ID`. The `GCP projects` allow you to organize and monitor more precisely how you consume the **GCP** resources. For the purpose of the bootcamp, we are only going to create a single project.
 
-  Now, we need a way to tell which ressources within a `GCP project` our code will be allowed to consume. Our code consumes GCP ressources through API calls.
+  Now, we need a way to tell which resources within a `GCP project` our code will be allowed to consume. Our code consumes GCP resources through API calls.
 
   Since API calls are not free, it is important to define with caution how our code will be allowed to use them. During the bootcamp this will not be an issue and we are going to allow our code to use all the API of **GCP** without any restrictions.
 
@@ -189,7 +189,7 @@ Since the [service account](https://cloud.google.com/iam/docs/service-accounts)
   - Click on **CREATE SERVICE ACCOUNT**:
   - Give a `Service account name` to that account
   - Click on **CREATE AND CONTINUE**
-  - Click on **Select a role** and choose `Quick access/Basic` then **Owner**, which gives full access to all ressources
+  - Click on **Select a role** and choose `Quick access/Basic` then **Owner**, which gives full access to all resources
   - Click on **CONTINUE**
   - Click on **DONE**
 - Download the service account json file 🔑:

_partials/gcp_setup_wsl.md

@@ -1,4 +1,4 @@
-We will now move the service account json file from your Windows disk to the Ubuntu disk. This will allow the development tools in Ubuntu to access to the ressources of your GCP account.
+We will now move the service account json file from your Windows disk to the Ubuntu disk. This will allow the development tools in Ubuntu to access to the resources of your GCP account.
 
 First, let's create a directory in which we will store the file.
 
@@ -73,4 +73,4 @@ You can do so by running
 code ~/.zshrc
 ```
 
-in the Terminal! 😄
+in the Terminal! 😄

_partials/keep_current.md

@@ -269,7 +269,7 @@ Make sure that the file contains the correct :
 
 👉 If this does not display anything or if the email inside of the file is not the one of your service account, go back to the setup
 
-Make sure that Docker recognizes the GCP ressources :
+Make sure that Docker recognizes the GCP resources :
 
 ``` bash
 gcloud auth configure-docker

macOS.md

@@ -1021,11 +1021,11 @@ Now that you have created a `GCP account` and a `project` (identified by its `PR
   <summary>🤔 Why do we need a service account key ?</summary>
 
 
-  You have created a `GCP account` linked to your credit card. Your account will be billed according to your usage of the ressources of the **Google Cloud Platform**. The billing will occur if you consume anything once the free trial is over, or if you exceed the amount of spending allowed during the free trial.
+  You have created a `GCP account` linked to your credit card. Your account will be billed according to your usage of the resources of the **Google Cloud Platform**. The billing will occur if you consume anything once the free trial is over, or if you exceed the amount of spending allowed during the free trial.
 
-  In your `GCP account`, you have created a single `GCP project`, identified by its `PROJECT_ID`. The `GCP projects` allow you to organize and monitor more precisely how you consume the **GCP** ressources. For the purpose of the bootcamp, we are only going to create a single project.
+  In your `GCP account`, you have created a single `GCP project`, identified by its `PROJECT_ID`. The `GCP projects` allow you to organize and monitor more precisely how you consume the **GCP** resources. For the purpose of the bootcamp, we are only going to create a single project.
 
-  Now, we need a way to tell which ressources within a `GCP project` our code will be allowed to consume. Our code consumes GCP ressources through API calls.
+  Now, we need a way to tell which resources within a `GCP project` our code will be allowed to consume. Our code consumes GCP resources through API calls.
 
   Since API calls are not free, it is important to define with caution how our code will be allowed to use them. During the bootcamp this will not be an issue and we are going to allow our code to use all the API of **GCP** without any restrictions.
 
@@ -1046,7 +1046,7 @@ Since the [service account](https://cloud.google.com/iam/docs/service-accounts)
   - Click on **CREATE SERVICE ACCOUNT**:
   - Give a `Service account name` to that account
   - Click on **CREATE AND CONTINUE**
-  - Click on **Select a role** and choose `Quick access/Basic` then **Owner**, which gives full access to all ressources
+  - Click on **Select a role** and choose `Quick access/Basic` then **Owner**, which gives full access to all resources
   - Click on **CONTINUE**
   - Click on **DONE**
 - Download the service account json file 🔑:

macOS_keep_current.md

@@ -245,7 +245,7 @@ Make sure that the file contains the correct :
 
 👉 If this does not display anything or if the email inside of the file is not the one of your service account, go back to the setup
 
-Make sure that Docker recognizes the GCP ressources :
+Make sure that Docker recognizes the GCP resources :
 
 ``` bash
 gcloud auth configure-docker