Apply suggestions from code review

Co-authored-by: Alan Poulain <[email protected]>

Author: soyuka

docs/adr/0001-resource-identifiers.md

@@ -1,24 +1,24 @@
-# Resource identifiers
+# Resource Identifiers
 
 * Status: proposed
 * Deciders: @dunglas @alanpoulain @soyuka
 
 Technical Story: [#2126][pull/2126]
-Implementation: [#3825][pull/3825 ]
+Implementation: [#3825][pull/3825]
 
 ## Context and Problem Statement
 
 In API Platform, a resource is identified by [IRIs][rfc/IRI], for example `/books/1`. Internally, this is also known as a route with an identifier parameter named `id`: `/books/{id}`. This `id` parameter is then matched to the resource identifiers, known by the `ApiProperty` metadata when `identifier` is true. When multiple identifiers are found, composite identifiers map the value of `id` to the resource identifiers (eg: `keya=value1;keyb=value2`, where `keya` and `keyb` are identifiers of the resource). This behavior is suggested by the [URI RFC][rfc/URI].
 Subresources IRIs have multiple parts, for example: `/books/{id}/author/{authorId}`. The router needs to know that `id` matches the `Book` resource, and `authorId` the `Author` resource. To do so, a Tuple representing the class and the property matching each parameter is linked to the route, for example: `id: [Book, id], authorId: [User, id]`.
-By normalizing the shape of (sub)-resources (see [0000-subresources-definition][0000-subresources-definition]), we need to normalize the resource identifiers.
+By normalizing the shape of (sub-)resources (see [0000-subresources-definition][0000-subresources-definition]), we need to normalize the resource identifiers.
 
 ## Decision Outcome
 
 Declare explicit resource `identifiers` that will default to `id: [id, Resource]` with composite identifiers. Allow composite identifiers to be disabled if needed.
 
 ### Examples
 
-Define a route `/users/{id}` 
+Define a route `/users/{id}`:
 
 ```php
 /**