FAB-16573 Removed "kind of a" node, and more

Signed-off-by: Paritosh Ranjan <paranjan@in.ibm.com>
Change-Id: If6f6cc547d774d65b7d8d485025f66bb83092a7d

Author: paranjan

docs/source/orderer/ordering_service.md

@@ -18,13 +18,12 @@ still vulnerable to divergent ledgers (also known as a ledger "fork"), where
 different participants in the network have a different view of the accepted
 order of transactions.
 
-Hyperledger Fabric works differently. It features a kind of a node called an
+Hyperledger Fabric works differently. It features a node called an
 **orderer** (it's also known as an "ordering node") that does this transaction
-ordering, which along with other nodes forms an **ordering service**. Because
-Fabric's design relies on **deterministic** consensus algorithms, any block a
-peer validates as generated by the ordering service is guaranteed to be final
-and correct. Ledgers cannot fork the way they do in many other distributed
-blockchains.
+ordering, which along with other orderer nodes forms an **ordering service**.
+Because Fabric's design relies on **deterministic** consensus algorithms, any block
+validated by the peer is guaranteed to be final and correct. Ledgers cannot fork
+the way they do in many other distributed and permissionless blockchain networks.
 
 In addition to promoting finality, separating the endorsement of chaincode
 execution (which happens at the peers) from ordering gives Fabric advantages