Merge pull request #272 from ably/269-fix-CHA-O4-subspecs-names

Replaced zeroes in CHA-O4 subspec names.

textile/chat-features.textile

@@ -442,10 +442,10 @@ the overhead of having everyone in presence.
 * @(CHA-O2)@ The occupancy event format is shown "here":#chat-structs-occupancy-event
 * @(CHA-O3)@ @[Testable]@ Users can request an instantaneous occupancy check via the REST API. The request is detailed "here":#rest-occupancy-request, with the response format being a simple "occupancy event":#chat-structs-occupancy-event
 * @(CHA-O4)@ Users can subscribe to in-band, realtime occupancy updates.
-** @(CHA-04a)@ @[Testable]@ Users may register a listener that receives occupancy events in realtime.
-** @(CHA-04b)@ @[Testable]@ A subscription to occupancy events may be removed, after which it shall receive no further events.
-** @(CHA-04c)@ @[Testable]@ When a regular occupancy event is received on the channel (a standard PubSub occupancy event per the docs), the SDK will convert it into "occupancy event":#chat-structs-occupancy-event format and broadcast it to subscribers.
-** @(CHA-04d)@ @[Testable]@ If an invalid occupancy event is received on the channel, it shall be dropped.
+** @(CHA-O4a)@ @[Testable]@ Users may register a listener that receives occupancy events in realtime.
+** @(CHA-O4b)@ @[Testable]@ A subscription to occupancy events may be removed, after which it shall receive no further events.
+** @(CHA-O4c)@ @[Testable]@ When a regular occupancy event is received on the channel (a standard PubSub occupancy event per the docs), the SDK will convert it into "occupancy event":#chat-structs-occupancy-event format and broadcast it to subscribers.
+** @(CHA-O4d)@ @[Testable]@ If an invalid occupancy event is received on the channel, it shall be dropped.
 to typing subscribers.
 * @(CHA-O5)@ @[Testable]@ Users may subscribe to discontinuity events to know when there's been a break in occupancy. Their listener will be called when a discontinuity event is triggered from the room lifecycle. For occupancy, there shouldn't need to be user action as most channels will send occupancy updates regularly as clients churn.