fix typo

cloudevents/spec.md

@@ -459,16 +459,16 @@ on the definition of OPTIONAL.
     the name of the newly created blob is carried in `subject`:
       - `source`: `https://example.com/storage/tenant/container`
       - `subject`: `mynewfile.jpg`
-  - A subscriber might register interest for when new updates are made to a client
-    in an eCommerce system. In this case, the event `source` identifies the
-    subscription scope (CRM part of an eCommerce system), the `type` identifies
-    the "client updated" event, and the `id` uniquely identifies the event
-    instance to distinguish separate occurrences of a same client being
-    updated multiple times; the `subject` uniquely identifies the client within
-    the scope of the `source` by including a "partner id" and "client id"
+  - A subscriber might register interest for when new updates are made to a
+    client in an eCommerce system. In this case, the event `source` identifies
+    the subscription scope (CRM part of an eCommerce system), the `type`
+    identifies the "client updated" event, and the `id` uniquely identifies
+    the event instance to distinguish separate occurrences of a same client
+    being updated multiple times; the `subject` uniquely identifies the client
+    within the scope of the `source` by including a "partner id" and "client id"
     (which is unique within the scope of the "partner id") separated by a colon:
       - `source`: `https://example.com/eCommerce/crm`
-      - `subject`: `partnerid/5/clientid/100`
+      - `subject`: `partnerid/5:clientid/100`
 
 #### time
 
@@ -567,11 +567,11 @@ compliance with these size constraints:
 - Intermediaries MUST forward events of a size of 64 KiB or less.
 - Consumers SHOULD accept events of a size of at least 64 KiB.
 
-In effect, these rules will allow producers to publish events up to 64 KiB in size
-safely. Safely here means that it is generally reasonable to expect the event to
-be accepted and retransmitted by all intermediaries. It is in any particular
-consumer's control, whether it wants to accept or reject events of that size due
-to local considerations.
+In effect, these rules will allow producers to publish events up to 64 KiB in
+size safely. Safely here means that it is generally reasonable to expect the
+event to be accepted and retransmitted by all intermediaries. It is in any
+particular consumer's control, whether it wants to accept or reject events of
+that size due to local considerations.
 
 Generally, CloudEvents publishers SHOULD keep events compact by avoiding
 embedding large data items into event payloads and rather use the event payload