docs: fix typos

Signed-off-by: vuittont60 <81072379+vuittont60@users.noreply.github.com>
hyperledger · Jan 9, 2024 · 9afc73d · 9afc73d
1 parent 16856f9
commit 9afc73d
Show file tree

Hide file tree

Showing 4 changed files with 5 additions and 5 deletions.
diff --git a/docs/source/commands/peerlifecycle.md b/docs/source/commands/peerlifecycle.md
@@ -512,7 +512,7 @@ This command will be useful, for example, in the following cases:
   * To check whether a particular chaincode package is installed or not without
   installing that package.
 
-Calcuate the package ID for the `mycc.tar.gz` package:
+Calculate the package ID for the `mycc.tar.gz` package:
 
 ```
 peer lifecycle chaincode calculatepackageid mycc.tar.gz

diff --git a/docs/source/orderer/ordering_service.md b/docs/source/orderer/ordering_service.md
@@ -39,7 +39,7 @@ policies that the relevant administrators set when they created the channel.
 Configuration transactions are processed by the orderer,
 as it needs to know the current set of policies to execute its basic
 form of access control. In this case, the orderer processes the
-configuration update to make sure that the requestor has the proper
+configuration update to make sure that the requester has the proper
 administrative rights. If so, the orderer validates the update request against
 the existing configuration, generates a new configuration transaction,
 and packages it into a block that is relayed to all peers on the channel. The
@@ -367,7 +367,7 @@ the BFT protocol withstands failures of up to (and not including) a third of the
 If a third or more of the nodes crash or are unreachable, no blocks can be agreed upon.
 
 The advantage of the BFT orderer over the Raft orderer is that it can withstand some of the nodes being compromised.
-Indeed, if up to (but not including) a third of the orderer nodes are controlled by a malicous party,
+Indeed, if up to (but not including) a third of the orderer nodes are controlled by a malicious party,
 the system can still accept new transactions, order them, and most importantly ensure the same blocks are committed
 by the rest of the ordering nodes. This is in contrast to Raft, which is not suitable to be deployed in such a harsh adversary model.
 

diff --git a/docs/source/prereqs.md b/docs/source/prereqs.md
@@ -147,7 +147,7 @@ Finally, you need to ensure Docker Desktop has integration enabled for your dist
 
 ### Microsoft VS Code (Optional)
 
-Microsoft VS Code provides an IDE that has tight integration with WSL2 Linux Distibutions. Search the Microsoft Marketplace in VS Code for the Remote Development extension pack for more information. This pack includes, among other things, the `Remote - WSL extension` and the `Remote - Containers` extension.
+Microsoft VS Code provides an IDE that has tight integration with WSL2 Linux Distributions. Search the Microsoft Marketplace in VS Code for the Remote Development extension pack for more information. This pack includes, among other things, the `Remote - WSL extension` and the `Remote - Containers` extension.
 
 ### Git For Windows (Optional)
 

diff --git a/docs/source/security_model.md b/docs/source/security_model.md
@@ -87,7 +87,7 @@ Ordering service nodes have an identity of their own, and are managed by an admi
 
 For more information see the [Ordering Nodes and Identity topic](./orderer/ordering_service.html#orderer-nodes-and-identity) and [Ordering Node Deployment and Administration topic](./deployorderer/ordererdeploy.html).
 
-## Tranport Layer Security (TLS)
+## Transport Layer Security (TLS)
 
 Fabric supports secure communication between nodes using Transport Layer Security (TLS).
 TLS communication can use both one-way (server only) and two-way (server and client) authentication.