diff --git a/src/en/clean-copy/03-Section II. The Backwards Compatibility/04.md b/src/en/clean-copy/03-Section II. The Backwards Compatibility/04.md
index c967350..3f4a384 100644
--- a/src/en/clean-copy/03-Section II. The Backwards Compatibility/04.md	
+++ b/src/en/clean-copy/03-Section II. The Backwards Compatibility/04.md	
@@ -203,11 +203,11 @@ We should also note that providing a newly created entity identifier by the requ
 ```
 POST /v1/recipes/custom
 {
-  // First part of the composite
+  // The first part of the composite
   // identifier, for example,
   // the partner's own id
   "namespace": "my-coffee-company",
-  // Second part of the identifier
+  // The second part of the identifier
   "id_component": "lungo-customato"
 }
 →
@@ -217,4 +217,4 @@ POST /v1/recipes/custom
 }
 ```
 
-Also note that this format allows us to maintain an important extensibility point: different partners might have totally isolated namespaces, or conversely share them. Furthermore, we might introduce special namespaces (like `common`, for example) to allow for publishing new recipes for everyone (and that, by the way, would allow us to organize our own backoffice to edit recipes).
\ No newline at end of file
+Also note that this format allows us to maintain an important extensibility point: different partners might have totally isolated namespaces or conversely share them. Furthermore, we might introduce special namespaces (like `common`, for example) to allow editing standard recipes (and thus organizing our own recipes backoffice).
\ No newline at end of file