Fix docs links and formatting
MODIFY
docs/api_specs/includes/operator_api_specs.md
docs/api_specs/includes/operator_api_specs.md
@@ -40,7 +40,7 @@ Attribute | Type | Description
--------- | ------- | -----------
transaction | Hex encoded string | Signed transaction RLP-encoded to bytes and HEX-encoded to string
-<aside class="notice">Normally you should call the Watcher's (Transaction - Submit)[#] instead of this. The Watcher's version performs various security and validation checks before submitting the transaction, so is much safer. However, if the Watcher is not available this version exists.</aside>
+<aside class="notice">Normally you should call the Watcher's <a href="#transaction-submit">Transaction - Submit</a> instead of this. The Watcher's version performs various security and validation checks before submitting the transaction, so is much safer. However, if the Watcher is not available this version exists.</aside>

MODIFY
docs/api_specs/includes/watcher_api_specs.md
docs/api_specs/includes/watcher_api_specs.md
@@ -36,7 +36,7 @@ curl -X POST -H "Content-Type: application/json" http://localhost:4000/account.g
```
Gets all utxos belonging to the given address.
-<aside class="notice"> Note that this is a performance intensive call and should only be used if the chain is byzantine and the user needs to retrieve utxo information to be able to exit. Normally an application should use the Informational API's (Account - Get Utxos)[#] This version is provided in case the Informational API is not available.</aside>
+<aside class="notice"> Note that this is a performance intensive call and should only be used if the chain is byzantine and the user needs to retrieve utxo information to be able to exit. Normally an application should use the Informational API's <a href="#cccount-get-utxos">Account - Get Utxos</a> instead. This version is provided in case the Informational API is not available.</aside>
### HTTP Request
@@ -354,6 +354,7 @@ An in-flight exit of a non-canonical transaction has been started. It should be
<aside class="warning"> Not Implemented Yet.</aside>
Event details:
+
Attribute | Type | Description
--------- | ------- | -----------
txbytes | Hex encoded string | The in-flight transaction that the event relates to
@@ -374,6 +375,7 @@ A canonical in-flight exit has been challenged. The challenge should be responde
<aside class="warning"> Not Implemented Yet.</aside>
Event details:
+
Attribute | Type | Description
--------- | ------- | -----------
txbytes | Hex encoded string | The in-flight transaction that the event relates to
@@ -401,6 +403,7 @@ An in-flight exit has been started and can be piggybacked. If all inputs are own
<aside class="warning"> Not Implemented Yet.</aside>
Event details:
+
Attribute | Type | Description
--------- | ------- | -----------
txbytes | Hex encoded string | The in-flight transaction that the event relates to
@@ -425,6 +428,7 @@ An invalid piggyback is in process. Should be challenged.
<aside class="warning"> Not Implemented Yet.</aside>
Event details:
+
Attribute | Type | Description
--------- | ------- | -----------
txbytes | Hex encoded string | The in-flight transaction that the event relates to

MODIFY
docs/api_specs/includes/watcher_websocket_specs.md
docs/api_specs/includes/watcher_websocket_specs.md
@@ -61,8 +61,6 @@ child_block_hash | HEX-encoded string |
submited_at_ethheight | integer |
tx | object | Structure of signed transaction
-Blocks are validated by the Watcher after a short (not-easily-configurable) finality margin. By consequence, above events will be emitted no earlier than that finality margin. In case extra finality is required for high-stakes transactions, the client is free to wait any number of Ethereum blocks (confirmations) on top of submitted_at_ethheight.
-
## Topic `childchain`

MODIFY
docs/api_specs/index.html.md
docs/api_specs/index.html.md
@@ -25,4 +25,4 @@ search: true
This is the HTTP-RPC API for the ChildChain and Watcher.
All calls use HTTP POST and pass options in the request body in JSON format.
-Errors will usually return with HTTP response code 200, and the details of the error in the response body. See (Errors)[#].
+Errors will usually return with HTTP response code 200, and the details of the error in the response body. See [Errors](#errors).

Fix docs links and formatting