Use names consistently

scaleway · Jul 7, 2018 · b443389 · b443389
1 parent ce1c774
commit b443389
Showing 1 changed file with 7 additions and 5 deletions.
diff --git a/website/docs/index.html.markdown b/website/docs/index.html.markdown
@@ -24,7 +24,7 @@ Here is an example that will setup the following:
 ```hcl
 provider "scaleway" {
   organization = "<YOUR-ORGANIZATION-ID>"
-  token        = "<YOUR-GENERATED-TOKEN>"
+  token        = "<YOUR-SECRET-TOKEN>"
   region       = "par1"
 }
 
@@ -82,13 +82,15 @@ Your **organization ID** can be found in the *Account* tab of the Scaleway contr
 is labeled "Organization ID". Alternatively, if you already have a **secret token** you can
 issue a request to the Scaleway API directly and query for your **organization ID**:
 ```shell
-$ curl https://account.scaleway.com/organizations -H "X-Auth-Token: <TOKEN_SECRET_KEY>"
+$ curl https://account.scaleway.com/organizations -H "X-Auth-Token: <YOUR-SECRET-TOKEN>"
 ```
 
 A **secret token** can be generated by visiting the *Credentials* tab of the Scaleway
-control panel and looking in the *Tokens* section at the bottom of the page. Secret keys
-are only revealed one time (when the key is first created) so create a new token if
-necessary. Giving each token a friendly-name is recommended.
+control panel and looking in the *Tokens* section at the bottom of the page. Each listed
+"Secret Key" (if any tokens have already been created) can be used as your **secret token**.
+Since secret keys are only revealed one time (when the token is first created) you might
+need to create a new token to get a new "Secret Key". Giving each token a friendly-name
+is recommended.
 
 If you do not want to put credentials in your configuration file,
 you can leave them out: