chore: remove repetitive words

Signed-off-by: dulanting <dulanting@outlook.jp>

Author: dulanting

full-stack-asset-transfer-guide/docs/CloudReady/20-fabric.md

@@ -89,7 +89,7 @@ We can then tail the org1-peer1 log in a terminal window so that we can see proo
 kubectl logs -f org1-peer1-79df64f8d8-7m9mt peer
 ```
 
-Now that you know how to use kubectl, let's learn the shortcut! You can easily monitor all of the the pods in the [k9s utility](https://k9scli.io/topics/install/). If you haven't started k9s yet, start it in a new terminal:
+Now that you know how to use kubectl, let's learn the shortcut! You can easily monitor all of the pods in the [k9s utility](https://k9scli.io/topics/install/). If you haven't started k9s yet, start it in a new terminal:
 
 ```shell
 k9s -n test-network

token-erc-1155/README.md

@@ -21,7 +21,7 @@ The following required functions of ERC-1155 are implemented:
 
 Note: The "safe" prefix is omitted from "TransferFrom" in the implementation because the prefix is related to some issue about backwards compatibility with older smart contracts in Ethereum.
 
-Note: TransferFrom is used to send a single token type between two users. BatchTransferFrom is used to send multiple tokens between two users. So, BatchTransferFrom is a more general form of TransferFrom. Ethereum defined two functions instead of one because this reduces gas costs. Since there is no gas cost in Fabric, implementing these two functions is unnecessary. Nevertheless, both of them are implemented to to conform the ERC-1155 standard.
+Note: TransferFrom is used to send a single token type between two users. BatchTransferFrom is used to send multiple tokens between two users. So, BatchTransferFrom is a more general form of TransferFrom. Ethereum defined two functions instead of one because this reduces gas costs. Since there is no gas cost in Fabric, implementing these two functions is unnecessary. Nevertheless, both of them are implemented to conform the ERC-1155 standard.
 
 ## Additional Functions Implemented