Change:
RFC8446. There are a number of data nodes defined in this YANG module that are <del> writable/creatable/deletable (i.e., config true, which is the </del> <ins> writable/creatable/deletable (i.e., _config true_, which is the </ins> default).  These data nodes may be considered sensitive or vulnerable <del> in some network environments.  Write operations (e.g., edit-config) </del> <ins> in some network environments.  Write operations (e.g., _edit-config_) </ins> to these data nodes without proper protection can have a negative effect on network operations.  These are the subtrees and data nodes <del> and their sensitivity/vulnerability: Container: '/rats-support-structures/attester-supported-algos' </del> <ins> as well as their sensitivity/vulnerability: </ins> 'tpm12-asymmetric-signing', 'tpm12-hash', 'tpm20-asymmetric- <del> signing', and 'tpm20-hash' all could be populated with algorithms which are not supported by the underlying physical TPM installed by the equipment vendor. Container: '/rats-support-structures/tpms' </del> <ins> signing', and 'tpm20-hash'.  All could be populated with algorithms that are not supported by the underlying physical TPM installed by the equipment vendor. </ins> <del> 'name' - Although shown as 'rw', it is system generated. Therefore it should not be possible for an operator to add or remove a TPM from the configuration. </del> <ins> 'name': Although shown as 'rw', it is system generated.  Therefore it should not be possible for an operator to add or remove a TPM from the configuration. </ins> <del> 'tpm20-pcr-bank' - It is possible to configure PCRs for extraction </del> <ins> 'tpm20-pcr-bank': It is possible to configure PCRs for extraction </ins> which are not being extended by system software.  This could unnecessarily use TPM resources. <del> 'certificates' - It is possible to provision a certificate which does not correspond to a Attestation Identity Key (AIK) within the TPM. </del> <ins> 'certificates': It is possible to provision a certificate which does not correspond to an Attestation Identity Key (AIK) within the TPM 1.2, or an Attestation Key (AK) within the TPM 2.0 respectively. </ins> <del> RPC: 'tpm12-challenge-response-attestation' - Need to verify that the certificate is provided is able to support Attestation on the targeted TPM. </del> <ins> It must be verified that the certificate is for an active AIK, i. e. the certificate provided is able to support Attestation on the targeted TPM 1.2. </ins> <del> RPC: 'tpm20-challenge-response-attestation' - Need to verify that the certificate is provided is able to support Attestation on the targeted TPM. </del> <ins> It must be verified that the certificate is for an active AK, i. e. the certificate provided is able to support Attestation on the targeted TPM 2.0. </ins> <del> RPC: 'log-retrieval' - Pulling lots of logs can chew up system resources. </del> <ins> Pulling lots of logs can chew up system resources. </ins> 5.

Discussion:
Basically, this fixes typos, grammar, and consistency. And, all above, the TPM 2.0 quote information, which was set to TPMSQUOTEINFO. Actually it is TPM2B_ATTEST. Further Issues to be created.
TPM 2.0 quote information (attestation data) is of type TPM2BATTEST, not TPMSQUOTEINFO. TPMSQUOTEINFO is a sub element of the TPM2BATTEST. In a TPM2Quote operation, the TPM signs a hash of the TPM2BATTEST structure. The signature is of type TPMT_SIGNATURE (just FYI).