Skip to content

Commit

Permalink
Typo resource io ressource
Browse files Browse the repository at this point in the history
  • Loading branch information
julesvanrie committed Aug 5, 2024
1 parent de97313 commit 136ef10
Show file tree
Hide file tree
Showing 3 changed files with 7 additions and 7 deletions.
8 changes: 4 additions & 4 deletions _partials/gcp_setup.md
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand All @@ -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 🔑:
Expand Down
4 changes: 2 additions & 2 deletions _partials/gcp_setup_wsl.md
Original file line number Diff line number Diff line change
@@ -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.

Expand Down Expand Up @@ -73,4 +73,4 @@ You can do so by running
code ~/.zshrc
```

in the Terminal! 😄
in the Terminal! 😄
2 changes: 1 addition & 1 deletion _partials/keep_current.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Expand Down

0 comments on commit 136ef10

Please sign in to comment.