anchor.diff:  
   ## Authentication
   Authentication is done via Storage API **Token**. There are multiple options
  -for [obtaining a Storage API Token](https://help.keboola.com/storage/tokens/). 
  +for [obtaining a Storage API Token](https://help.keboola.com/storage/tokens/).
   The token must be sent as a value of the `X-StorageApi-Token` HTTP header with each API call.
   
   Most API calls work within a *KBC Project*. The project is always derived from the token used for the API call.
   So the token includes both authentication and authorization to a single project.
   
   ## Synchronous and Asynchronous Calls
  -Calls that represent potentially long-running actions are performed asynchronously. 
  +Calls that represent potentially long-running actions are performed asynchronously.
   These are for example: loading table data, snapshotting, exporting table data, table structure modifications, etc.
  -All asynchronous calls return the HTTP Response code `202` and a [Job Resource](#reference/jobs). 
  -To obtain the actual result of the call, you have to monitor the job status by 
  +All asynchronous calls return the HTTP Response code `202` and a [Job Resource](#reference/jobs).
  +To obtain the actual result of the call, you have to monitor the job status by
   [polling the Job Resource URL](https://developers.keboola.com/integrate/storage/api/import-export/#python-example).
   
   ## Partial Response
  -Some API calls that list objects are returning related resources by default. For example, 
  +Some API calls that list objects are returning related resources by default. For example,
   the [table list](#reference/tables/create-or-list-tables/tables-in-bucket) also returns
  -the table bucket properties and table attributes. You can use the `include` parameter 
  +the table bucket properties and table attributes. You can use the `include` parameter
   to return only the required resources in the response.
   
   # Group Maintenance
  
positive.code: 
  # Group Metadata
  You can associate custom metadata with buckets, tables or columns.
  Metadata are timestamped key-value pairs separated by the provider, where the provider is the originating component. 
  Metadata allows you to assign custom information to your resources. Bucket attributes methods are described 
  below. Work with table and column metadata in the same manner; simply use a table or column instead of a bucket in the url.
  
  ## Bucket Metadata [/v2/storage/buckets/{bucket_id}/metadata]
  
  ### Create or Update [POST]
  Sets multiple metadata with one call. If the given key and provider combination already exist 
  for the bucket, the data will be updated with the new value and timestamp. All metadata associated 
  with the bucket are returned in the response.
  
  + Parameters
  
negative.code:     + workspace_id (required, number)
  
  ### Load Data [POST]
  Loads tables from Storage into a Workspace.
  
  + Attributes
      + input[] (required, array) - Mappings of source tables with destinations to be loaded into the workspace
  