Fix wording

Author: xxuejie

rfcs/0000-cighash-all/0000-cighash-all.md

@@ -53,10 +53,10 @@ For a CKB transaction, `CIGHASH_ALL` utilities the following workflow:
 
 There are several notable points worth mentioning regarding the above specification:
 
-* The first witness of current running script group must be a valid [WitnessArgs] structure serialized in the molecule serialization format. There shall be not assumptions with respect to this rule.
-* The content of all input cells are all covered by any signature guarding a particular CKB transaction, making it much easier to design an offline signing scheme.
+* The first witness of current running script group must be a valid [WitnessArgs](https://github.com/nervosnetwork/ckb/blob/81a1b9a1491edca0bc42c12d8bf0f715a055a93f/util/gen-types/schemas/blockchain.mol#L114-L118) structure serialized in the molecule serialization format. This has now become an enforce rule, it is not an assumption that can be exploited or ignored.
+* The content of all input cells are covered by the message calculation workflow, making it much easier to design an offline signing scheme.
 * Witness length is packed in 32-bit unsigned integers, while 64-bit unsigned integers were used in older workflow.
-* A different concatenation/hashing design is introduced for the first witness of the current script group, here we discard the zero-filled design, in favor of a different solution that only includes selective, useful bytes, this can contribute to a more optimized implementation, both in terms of runtime cycles and binary size.
+* A different concatenation/hashing design is introduced for the first witness of the current script group, discarding the original zero-filled design. We believe this new solution can contribute to a more optimized implementation, both in terms of runtime cycles and binary size.
 
 ## Examples