While touching this paragraph, there are other fixups that can be made:
0 The scope of this proposal is deliberately kept narrow; it addresses
1 only spending of transaction outputs containing P2C tweaks - and does not
2-addresses construction of a new P2C commitments or transactions containing them
3+address construction of new P2C commitments or transactions containing them
4 in their outputs.<ref>'''Why only spending of P2C tweaked outputs is covered'''
5-P2C tweaks commit to external data, some of which may represent certain value
6+P2C tweaks commit to external data, some of which may represent certain values
7 (like in some sidechains, single-use-seal applications like RGB etc). Creation
8-of such outputs much allow hardware devices to understand the structure of such
9+of such outputs allows hardware devices to understand the structure of such
10 extra-transaction data, which may be in different formats and constantly
11-involve. Thus, this should be addresses with a separate standards (or be a
12+involve. Thus, this should be addresses with a separate standard (or be
13 vendor-based). The current proposal only touches the question of spending an
14-output which contained previously created P2C commitment, which does not creates
15-a new commitment and does not provides that kind of risk of extra-blockchain
16-value loses.</ref>
17+output that contained previously created P2C commitments, which does not create
18+a new commitment and does not provide that kind of risk of extra-blockchain
19+value losses.</ref>
