anchor.diff:  // TEST[skip:we don't have gcs setup while testing this]
   
   The `credentials_file` settings are {ref}/secure-settings.html#reloadable-secure-settings[reloadable].
  -After you reload the settings, the internal `gcs` clients, used to transfer the
  -snapshot contents, will utilize the latest settings from the keystore.
  -
  -
  -NOTE: In progress snapshot/restore jobs will not be preempted by a *reload*
  -of the client's `credentials_file` settings. They will complete using the client
  -as it was built when the operation started.
  +After you reload the settings, the internal `gcs` clients, which are used to 
  +transfer the snapshot contents, utilize the latest settings from the keystore.
  +
  +NOTE: Snapshot or restore jobs that are in progress are not preempted by a *reload*
  +of the client's `credentials_file` settings. They complete using the client as 
  +it was built when the operation started.
   
   [[repository-gcs-client]]
   ==== Client Settings
   
   The client used to connect to Google Cloud Storage has a number of settings available.
  -Client setting names are of the form `gcs.client.CLIENT_NAME.SETTING_NAME` and specified
  +Client setting names are of the form `gcs.client.CLIENT_NAME.SETTING_NAME` and are specified
   inside `elasticsearch.yml`. The default client name looked up by a `gcs` repository is
   called `default`, but can be customized with the repository setting `client`.
   
  
positive.code: // TEST[skip:we don't have gcs setup while testing this]
  
  Some settings are sensitive and must be stored in the
  {ref}/secure-settings.html[elasticsearch keystore]. This is the case for the service account file:
  
  [source,sh]
  ----
  
negative.code: 
  `project_id`::
  
      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.
  
  