Fix typos

docs/metrics.md

@@ -63,7 +63,7 @@ If 'signer_total_sentry_connect_tries' is significant, it can indicate network o
 
 ## Watching Cosigner With Grafana
 
-A sample Grafana configration is available.  See [`horcrux.json`](https://github.com/chillyvee/horcrux-info/blob/master/grafana/horcrux.json)
+A sample Grafana configuration is available.  See [`horcrux.json`](https://github.com/chillyvee/horcrux-info/blob/master/grafana/horcrux.json)
 
 
 ## Watching For Cosigner Trouble

docs/signing.md

@@ -9,7 +9,7 @@ To provide private key security, The key is sharded into multiple pieces using [
 
 Each piece of the key is added to a relative signer node that will run the horcrux application. These signer nodes are part of an overall Horcrux cluster that will communicate with each other to sign each block, as requested by the configured sentry node(s).
 
-A higher threshold _`t`_ equates to more security, since more pieces of the key will be required to assemble a full signature. A higher threshold also means the fault tolerance is lower since you cannot tolerate as many missing participants, or in Horcrux' case, failed nodes. It is important to think about your specific use case to determine what the balance of _`n`_ and _`t`_. 
+A higher threshold _`t`_ equates to more security, since more pieces of the key will be required to assemble a full signature. A higher threshold also means the fault tolerance is lower since you cannot tolerate as many missing participants, or in Horcrux's case, failed nodes. It is important to think about your specific use case to determine what the balance of _`n`_ and _`t`_. 
 
 > IMPORTANT: For security and to ensure that there cannot be a situation in which there are two separate clusters of signer nodes that could combine a full signature, it is required that _`t > n/2`_