anchor.diff:  
   == Metadata Database
   
  -The metadata database maintains the knowledge of which buckets exist, and which versioned items belong to which buckets, as well as the version
  -history for each item.
  -
  -Currently NiFi Registry supports H2 or Postgres for the relational database engine (0.1.0 only supports H2).
  +The metadata database maintains the knowledge of which buckets exist, which versioned items belong to which buckets, as well as the version history for each item.
  +
  +Currently, NiFi Registry supports H2 or Postgres for the relational database engine.
  +
  +NOTE: NiFi Registry 0.1.0 only supports H2.
   
   == H2
   
  -H2 is an embedded database that is pre-configured in the default `nifi-registry.properties file`. The contents of the H2 database are stored in a file on the local filesystem.
  +H2 is an embedded database that is pre-configured in the default _nifi-registry.properties_ file. The contents of the H2 database are stored in a file on the local filesystem.
   
   For NiFi Registry 0.1.0, the location of the H2 database is specified by the property:
   
  
positive.code: [options="header,footer"]
  |==================================================================================================================================================
  | Property Name | Description
  |`Whitelisted Event Type` | EventTypes the hook provider configured with this property should respond to. If this property is left blank or not provided all events will fire for the configured hook provider. Multiple 'Whitelisted Event Type' can be specified and often are.
  EX: <property name="Whitelisted Event Type 1">CREATE_FLOW</property> and <property name="Whitelisted Event Type 2">UPDATE_FLOW</property> would invoke the configured hook provider for the CREATE_FLOW and UPDATE_FLOW EventTypes.
  |==================================================================================================================================================
  
  === ScriptEventHookProvider
  Hook provider for invoking a shell script that has been written by a user and placed on a file system that is accessible
  by the NiFi Registry instance that the provider is configured for.
  
  ....
  
negative.code: |`Region`|REQUIRED: The name of the S3 region where the bucket exists.
  |`Bucket Name`|REQUIRED: The name of an existing bucket to store extension bundles.
  |`Key Prefix`|An optional prefix that if specified will be added to the beginning of all S3 keys.
  |`Credentials Provider`|REQUIRED: Indicates how credentials will be provided, must be a value of `DEFAULT_CHAIN` or `STATIC`. `DEFAULT_CHAIN` will consider in order: Java system properties, environment variables, credential profiles (`~/.aws/credentials`). `STATIC` requires that `Access Key` and `Secret Access Key` be specified directly in this file.
  |`Access Key`| The access key to use when using `STATIC` credentials provider.
  |`Secret Access Key`| The secret access key to use when using `STATIC` credentials provider.
  |`Endpoint URL`| An optional URL that overrides the default AWS S3 endpoint URL. Set this when using an AWS S3 API compatible service hosted at a different URL.
  |====
  
  