Some amendments

Author: CarlosLopezDeLara

doc/stake-pool-operations/KES_period.md

@@ -25,7 +25,7 @@ cat mainnet-shelley-genesis.json | grep KES
 "maxKESEvolutions": 62,
 ```
 
-The key will evolve after each period of 129600 slots and it can evolve up-to 62 times before it needs to be renewed.
+The key will evolve after each period of 129600 slots and it can evolve up to 62 times before it needs to be renewed.
 
 Before we can create an operational certificate for our node, we need to figure out the start of the KES validity period, i.e. which KES evolution period we are in.
 
@@ -94,7 +94,7 @@ cardano-cli query kes-period-info --testnet-magic 42 --op-cert-file node-spo3/op
 **NOTE:** When your pool has already forged a block in the current KES interval these values must match.
 
 
-If your pool has **not** yet forged a block in the current KES Intervalit is ok that `cardano-cli query kes-period-info` shows that `"qKesOnDiskOperationalCertificateNumber"` is greater than `"qKesNodeStateOperationalCertificateNumber"` by exactly one (+1), for example:
+If your pool has **not** yet forged a block in the current KES Interval it's ok that `cardano-cli query kes-period-info` shows that `"qKesOnDiskOperationalCertificateNumber"` is greater than `"qKesNodeStateOperationalCertificateNumber"` by exactly one (+1), for example:
 
 ```
 "qKesNodeStateOperationalCertificateNumber": 2,
@@ -108,7 +108,7 @@ If your pool has **not** yet forged a block in the current KES Intervalit is ok
     --kes-period 205 \
     --out-file opcert.cert
 ```
-Nothing to worry about, when your pool forges a block `qKesNodeStateOperationalCertificateNumber` will be updated accordingly and these values will be the same.
+When your pool forges a block `qKesNodeStateOperationalCertificateNumber` will be updated accordingly and these values will be the same.
 
 ### How do I know if I have issued an _invalid_ operational certificate