3GPP 21.900 v20.0.0 — the document's own text
4.6.3 Contents of Change Requests
Taught in 5. The Change Request, field by field (How standards actually get made, in depth), 4. The change request and the release (How standards actually get made, overview).
Although the CR form shall indicate the details of change, each CR shall have attached the clauses of the specification that are affected by the CR, using the latest version of the major version. These clauses shall have the proposed modifications clearly marked, by means of the word processor's "revision mode".
In case there are more than one independent CR to the same part of the specification, neither of them should contain the proposed modifications from the other(s), however any potential interaction between the modifications should of course be resolved before presentation.
If the CR proposes changes to stage 3 specification files which are normatively documented in the 3GPP Forge repository according to clause 5C, then the proposed modifications shall be documented in the 3GPP Forge repository. In this case the cover page of the CR form shall contain a reference to a Forge Merge-Request clearly listing the proposed modifications in the "Other comments:" field, and excerpts of all affected stage 3 specification files clearly showing the proposed changes shall be appended to the cover page of the CR form.