README.md in avro_turf-1.14.0 vs README.md in avro_turf-1.15.0

@@ -151,9 +151,13 @@
 
 By default, AvroTurf will encode data in the Avro data file format. This means that the schema used to encode the data is prepended to the output. If you want to decrease the size of the output, e.g. when storing data in a log such as Apache Kafka or in a database, you can use the `AvroTurf::Messaging` API. This top-level API requires the use of [Schema Registry](https://github.com/confluentinc/schema-registry), a service which allows registering and fetching Avro schemas.
 
 The Messaging API will automatically register schemas used for encoding data, and will fetch the corresponding schema when decoding. Instead of including the full schema in the output, only a schema id generated by the registry is included. Registering the same schema twice is idempotent, so no coordination is needed.
 
+An optional `schema_context` parameter allows the registry to be scoped to a
+[schema context](https://docs.confluent.io/platform/7.5/schema-registry/schema-linking-cp.html#schema-contexts).
+If there is a need to access multiple contexts, you will need to use multiple instances of `ConfluentSchemaRegistry`.
+
 **NOTE:** [The Messaging format](https://github.com/confluentinc/schema-registry/blob/master/docs/serializer-formatter.rst#wire-format) is _not_ compatible with the Avro data file API.
 
 The Messaging API is not included by default, so you must require 'avro_turf/messaging' explicitly if you want to use it.
 
 Using the Messaging API is simple once you have set up a Schema Registry service: