fix(docs): fix format

Author: stevenj

docs/src/architecture/08_concepts/signed_doc/docs/contest_delegation.md

@@ -70,12 +70,12 @@ with the highest priority.
 * The [`parameters`](../metadata.md#parameters) metadata *MUST* point to the same Contest as the
     Nomination of the Representative.
 * The 'ref' metadata field MUST point to a valid 'Representative Nomination'.
-  * IF there are multiple representatives, then any which are not pointing
-      to a valid `Representative Nomination` are excluded.
-      The nomination is only invalid if ALL references `Representative Nomination`
-      references are invalid.
-      This is to prevent a Representative changing their nomination invalidating a
-      delegation with multiple representatives.
+    IF there are multiple representatives, then any which are not pointing
+    to a valid `Representative Nomination` are excluded.
+    The nomination is only invalid if ALL references `Representative Nomination`
+    references are invalid.
+    This is to prevent a Representative changing their nomination invalidating a
+    delegation with multiple representatives.
 * The payload MUST be nil.
 
 A Representative *MUST* Delegate to their latest Nomination for a Category,

specs/definitions/signed_docs/docs/contest_delegation.cue

@@ -62,12 +62,12 @@ docs: "Contest Delegation": {
 			* The `parameters` metadata *MUST* point to the same Contest as the 
 				Nomination of the Representative.
 			* The 'ref' metadata field MUST point to a valid 'Representative Nomination'.
-			    * IF there are multiple representatives, then any which are not pointing
-				  to a valid `Representative Nomination` are excluded.  
-				  The nomination is only invalid if ALL references `Representative Nomination` 
-				  references are invalid.
-				  This is to prevent a Representative changing their nomination invalidating a
-				  delegation with multiple representatives.
+			    IF there are multiple representatives, then any which are not pointing
+			    to a valid `Representative Nomination` are excluded.  
+			    The nomination is only invalid if ALL references `Representative Nomination` 
+			    references are invalid.
+			    This is to prevent a Representative changing their nomination invalidating a
+			    delegation with multiple representatives.
 			* The payload MUST be nil.
 
 			A Representative *MUST* Delegate to their latest Nomination for a Category,

specs/signed_doc.json

@@ -1593,7 +1593,7 @@
         }
       },
       "type": "764f17fb-cc50-4979-b14a-b213dbac5994",
-      "validation": "* The `parameters` metadata *MUST* point to the same Contest as the \n\tNomination of the Representative.\n* The 'ref' metadata field MUST point to a valid 'Representative Nomination'.\n    * IF there are multiple representatives, then any which are not pointing\n\t  to a valid `Representative Nomination` are excluded.  \n\t  The nomination is only invalid if ALL references `Representative Nomination` \n\t  references are invalid.\n\t  This is to prevent a Representative changing their nomination invalidating a\n\t  delegation with multiple representatives.\n* The payload MUST be nil.\n\nA Representative *MUST* Delegate to their latest Nomination for a Category,\notherwise their Nomination is invalid.\n\nThis is because Delegation points to a *SPECIFIC* Nomination, and it\n*MUST* be the latest for the Representative on the Contest.\nAs the Nomination contains information that the User relies on\nwhen choosing to delegate, changing that information could have a \nreal and detrimental result in the Delegation choice.\nTherefore, for a Delegation to be valid, it *MUST* point to the\nlatest Nomination for a Representative.\n\nPublishing a newer version of the Nomination Document to a specific contest will\ninvalidate all pre-existing delegations, and all voters will need\nto re-delegate to affirm the delegates latest nomination.\n\nA Voter may withdraw their Delegation by revoking all delegation documents.\n`revocations` must be set to `true` to withdraw a delegation, OR\na later contest delegation may change the delegated representative without\nfirst revoking the prior delegation, as only the latest delegation is\nconsidered.",
+      "validation": "* The `parameters` metadata *MUST* point to the same Contest as the \n\tNomination of the Representative.\n* The 'ref' metadata field MUST point to a valid 'Representative Nomination'.\n    IF there are multiple representatives, then any which are not pointing\n    to a valid `Representative Nomination` are excluded.  \n    The nomination is only invalid if ALL references `Representative Nomination` \n    references are invalid.\n    This is to prevent a Representative changing their nomination invalidating a\n    delegation with multiple representatives.\n* The payload MUST be nil.\n\nA Representative *MUST* Delegate to their latest Nomination for a Category,\notherwise their Nomination is invalid.\n\nThis is because Delegation points to a *SPECIFIC* Nomination, and it\n*MUST* be the latest for the Representative on the Contest.\nAs the Nomination contains information that the User relies on\nwhen choosing to delegate, changing that information could have a \nreal and detrimental result in the Delegation choice.\nTherefore, for a Delegation to be valid, it *MUST* point to the\nlatest Nomination for a Representative.\n\nPublishing a newer version of the Nomination Document to a specific contest will\ninvalidate all pre-existing delegations, and all voters will need\nto re-delegate to affirm the delegates latest nomination.\n\nA Voter may withdraw their Delegation by revoking all delegation documents.\n`revocations` must be set to `true` to withdraw a delegation, OR\na later contest delegation may change the delegated representative without\nfirst revoking the prior delegation, as only the latest delegation is\nconsidered.",
       "versions": [
         {
           "changes": "* First Published Version",