fixup! Add README describing TAMS

README.md

@@ -36,7 +36,8 @@ The process of writing to the store is:
 5. Client breaks content into segments as instructed and uploads it
 6. Client makes requests to [`POST flows/<flow_id>/segments`]() with details of each new segment created, to register them on the timeline
 
-### Flows and Sources and Mutation
+
+### Flows, Sources and Mutation
 Flows in the store are assumed to be immutable: once a grain has been written to a point on the timeline on a specific Flow, it cannot be changed. However Flows can always be extended, with empty spaces on the timeline filled in, and areas of the timeline can be permanently erased.
 
 When it becomes necessary to mutate content, for example reversioning content or performing production operations, the Flow ID (and potentially Source ID) will change. Various scenarios are explored in the [Practical Guidance for Media](https://specs.amwa.tv/ms-04/releases/v1.0.0/docs/3.0._Practical_Guidance_for_Media.html) section of AMWA MS-04.