anchor.diff:  
   `project_id`::
   
  -    The Google Cloud project id. This will be automatically infered from the credentials file but
  +    The Google Cloud project id. This will be automatically inferred from the credentials file but
       can be specified explicitly. For example, it can be used to switch between projects when the
       same credentials are usable for both the production and the development projects.
   
  
positive.code:   "private_key_id": "...",
    "private_key": "-----BEGIN PRIVATE KEY-----\n...\n-----END PRIVATE KEY-----\n",
    "client_email": "service-account-for-your-repository@your-project-id.iam.gserviceaccount.com",
    "client_id": "..."
  }
  ----
  // NOTCONSOLE
  
  This file must be stored in the {ref}/secure-settings.html[elasticsearch keystore], under a setting name
  of the form `gcs.client.NAME.credentials_file`, where `NAME` is the name of the client configuration.
  The default client name is `default`, but a different client name can be specified in repository
  settings using `client`.
  
  For example, if specifying the credentials file in the keystore under
  `gcs.client.my_alternate_client.credentials_file`, you can configure a repository to use these
  credentials like this:
  
  [source,js]
  ----
  
negative.code: 
  The service account used to access the bucket must have the "Writer" access to the bucket:
  
  1. Connect to the https://console.cloud.google.com/[Google Cloud Platform Console].
  2. Select your project.
  3. Got to the https://console.cloud.google.com/storage/browser[Storage Browser].
  4. Select the bucket and "Edit bucket permission".
  5. The service account must be configured as a "User" with "Writer" access.
  