diff --git a/README.md b/README.md
index 3fd000278..f3b7d84b5 100644
--- a/README.md
+++ b/README.md
@@ -102,10 +102,6 @@ Check out the [examples](https://github.com/asyncapi/asyncapi/blob/master/exampl
     <img src="./assets/ibm.png" alt="IBM logo" height="70">
   </a>
   &nbsp;&nbsp;&nbsp;&nbsp;
-<a href="https://iqvia.com" target="_blank">
-    <img src="./assets/iqvia.png" alt="IQVIA logo" height="60">
-  </a>
-  &nbsp;&nbsp;&nbsp;&nbsp;
 <a href="https://postman.com" target="_blank">
     <img src="./assets/postman.png" alt="Postman logo" height="90">
   </a>
@@ -131,6 +127,10 @@ Check out the [examples](https://github.com/asyncapi/asyncapi/blob/master/exampl
     <img src="./assets/bump-sh-white-bg.png" alt="Bump.sh logo" height="70">
   </a>
   &nbsp;&nbsp;&nbsp;&nbsp;
+  <a href="https://www.svix.com/" target="_blank">
+    <img src="./assets/swix.png" alt="swix logo" height="70">
+  </a>
+  &nbsp;&nbsp;&nbsp;&nbsp;
 
 </p>
 
diff --git a/assets/swix.png b/assets/swix.png
new file mode 100644
index 000000000..88325e9dd
Binary files /dev/null and b/assets/swix.png differ
diff --git a/examples/gitter-streaming.yml b/examples/gitter-streaming.yml
index 444bc9b81..b1dd57b29 100644
--- a/examples/gitter-streaming.yml
+++ b/examples/gitter-streaming.yml
@@ -160,5 +160,9 @@ components:
     streamingHeaders:
       http:
         headers:
-          'Transfer-Encoding': 'chunked'
-          Trailer: '\r\n'
+          type: object
+          properties:
+            'Transfer-Encoding':
+              const: 'chunked'
+            Trailer:
+              const: '\r\n'
diff --git a/spec/asyncapi.md b/spec/asyncapi.md
index 26bbd7f33..e57815747 100644
--- a/spec/asyncapi.md
+++ b/spec/asyncapi.md
@@ -595,7 +595,7 @@ Describes the operations available on a single channel.
 
 Field Name | Type | Description
 ---|:---:|---
-<a name="channelItemObjectRef"></a>$ref | `string` | Allows for a referenced definition of this channel item. The referenced structure MUST be in the form of a [Channel Item Object](#channelItemObject). In case a Channel Item Object field appears both in the defined object and the referenced object, the behavior is _undefined_. Resolution is done as defined by the [JSON Reference](https://tools.ietf.org/html/draft-pbryan-zyp-json-ref-03). <br/><br/>**Deprecated:** Usage of the `$ref` property has been deprecated.
+<a name="channelItemObjectRef"></a>$ref | `string` | Allows for a referenced definition of this channel item. The referenced structure MUST be in the form of a [Channel Item Object](#channelItemObject). In case a Channel Item Object field appears both in the defined object and the referenced object, the behavior is _undefined_. Resolution is done as defined by the [JSON Reference](https://tools.ietf.org/html/draft-pbryan-zyp-json-ref-03). <br/><br/>**Deprecated:** Using the $ref property with other properties is deprecated since the 2.3.0 version of the specification.
 <a name="channelItemObjectDescription"></a>description | `string` | An optional description of this channel item. [CommonMark syntax](https://spec.commonmark.org/) can be used for rich text representation.
 <a name="channelItemObjectServers"></a>servers | [`string`] | The servers on which this channel is available, specified as an optional unordered list of names (string keys) of [Server Objects](#serverObject) defined in the [Servers Object](#serversObject) (a map). If `servers` is absent or empty then this channel must be available on all servers defined in the [Servers Object](#serversObject).
 <a name="channelItemObjectSubscribe"></a>subscribe | [Operation Object](#operationObject) | A definition of the SUBSCRIBE operation, which defines the messages produced by the application and sent to the channel.