Conventions/CR-form-conventions.md

@@ -19,12 +19,12 @@ Changes to attachments should be given in the CR, after any changes to the prose
 
 > **EXAMPLE**
 >
-> For the change above, the first change block would be the changes to the prose in clause 6.
-> The change to the attachment would be given in the second change block, which would be indicated
-> as follows:
+> For the change above, the first change block would be the changes to the prose in clause 6. The change to the attachment would be given in the second change block, which would be indicated as follows:
 >
 > **--- SECOND CHANGE (LI-PS-PDU.ASN) ---**
+>
 > { changes} 
+>
 > **--- END OF CHANGES ---**
 
 The content of the change block can be given in one of two ways:
@@ -38,12 +38,10 @@ Each is described below:
 
 The CR author obtains a standard diff file that describes the changes to each attachment. For CR authors using the Forge web UI, this can be done from the Merge Request page.
 
-img tbd
+![image](uploads/483f3b6408bbbc938e46aa5cd1c6242c/image.png)
 
 The diff file will contain a set of changes to all the attachments affected by the CR. The CR author can then take the set of changes for each attachment and put them in a change block for that attachment. An example is given below:
 
-![image](uploads/e09302da05c8fa14e158b7e8a09bdb45/image.png)
-
 ### Showing changes to attachments via track changes
 
 The CR author can obtain the changes in Word track-changes format by downloading the post-build artefacts from the Merge Request front page.
@@ -61,8 +59,6 @@ If this method is used, the CR author **must copy the entire attachment into the
 in the "Other comments" field:
 
 * A reference to the Merge Request associated with the CR
-
-
 * A reference to the **latest** commit hash for that Merge Request.
 
 For consistency, CR authors should adopt the following convention when writing the text to go in the "Comments" field: