fixes

Author: bogdan-rosianu

docs/developers/data/composite-values.md

@@ -26,18 +26,17 @@ Then, all nested encodings of the items, concatenated.
 **Examples**
 
 | Type             | Value                | Top-level encoding    | Nested encoding                | Explanation                                                                                                                               |
-| 
-
----
-
-------------- | -------------------- | --------------------- | ------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------- |
+|
+| ---------------- | -------------------- | --------------------- | ------------------------------ | ----------------------------------------------------------------------------------------------------------------------------------------- |
 | `Vec<u8>`        | `vec![1, 2]`         | `0x0102`              | `0x00000002 0102`              | Length = `2`                                                                                                                              |
 | `Vec<u16>`       | `vec![1, 2]`         | `0x00010002`          | `0x00000002 00010002`          | Length = `2`                                                                                                                              |
 | `Vec<u16>`       | `vec![]`             | `0x`                  | `0x00000000`                   | Length = `0`                                                                                                                              |
 | `Vec<u32>`       | `vec![7]`            | `0x00000007`          | `0x00000001 00000007`          | Length = `1`                                                                                                                              |
 | `Vec< Vec<u32>>` | `vec![ vec![7]]`     | `0x00000001 00000007` | `0x00000001 00000001 00000007` | There is 1 element, which is a vector. In both cases the inner Vec needs to be nested-encoded in the larger Vec.                          |
 | `Vec<&[u8]>`     | `vec![ &[7u8][..]]`  | `0x00000001 07`       | `0x00000001 00000001 07`       | Same as above, but the inner list is a simple list of bytes.                                                                              |
-| `Vec< BigUint>`  | `vec![ 7u32.into()]` | `0x00000001 07`       | `0x00000001 00000001 07`       | `BigUint`s need to encode their length when nested. The `7` is encoded the same way as a list of bytes of length 1, so the same as above. |---
+| `Vec< BigUint>`  | `vec![ 7u32.into()]` | `0x00000001 07`       | `0x00000001 00000001 07`       | `BigUint`s need to encode their length when nested. The `7` is encoded the same way as a list of bytes of length 1, so the same as above. |
+
+---
 
 [comment]: # (mx-context-auto)
 

docs/developers/data/simple-values.md

@@ -35,11 +35,8 @@ Even when simulating smart contract execution on 64-bit systems, they must still
 **Examples**
 
 | Type    | Number                | Top-level encoding   | Nested encoding      |
-| 
-
----
-
----- | --------------------- | -------------------- | -------------------- |
+|
+| ------- | --------------------- | -------------------- | -------------------- |
 | `u8`    | `0`                   | `0x`                 | `0x00`               |
 | `u8`    | `1`                   | `0x01`               | `0x01`               |
 | `u8`    | `0x11`                | `0x11`               | `0x11`               |
@@ -94,7 +91,9 @@ Even when simulating smart contract execution on 64-bit systems, they must still
 | `isize` | `-0x11`               | `0xEF`               | `0xFFFFFFEF`         |
 | `isize` | `-0x1122`             | `0xEEDE`             | `0xFFFFEEDE`         |
 | `isize` | `-0x112233`           | `0xEEDDCD`           | `0xFFEEDDCD`         |
-| `isize` | `-0x11223344`         | `0xEEDDCCBC`         | `0xEEDDCCBC`         |---
+| `isize` | `-0x11223344`         | `0xEEDDCCBC`         | `0xEEDDCCBC`         |
+
+---
 
 [comment]: # (mx-context-auto)
 

docs/developers/toolchain-setup.md

@@ -87,12 +87,12 @@ Default host: x86_64-unknown-linux-gnu
 rustup home:  /home/ubuntu/.rustup
 
 installed toolchains
----
------------------
+--------------------
 stable-x86_64-unknown-linux-gnu (default)
 [...]
 
-active toolchain----------------
+active toolchain
+----------------
 name: stable-x86_64-unknown-linux-gnu
 installed targets:
   wasm32-unknown-unknown

docs/developers/tutorials/interactors-guide.md

@@ -271,9 +271,7 @@ test integration_test ... ok
 
 successes:
 
----
-
-- integration_test stdout ----
+---- integration_test stdout ----
 sender's recalled nonce: 1720
 -- tx nonce: 1720
 sc deploy tx hash: ca6e69c18acd73b20bfd21142b45be1b530ecbec89d1eb9c374b93f7681dbc38

docs/sdk-and-tools/rest-api/transactions.mdx

@@ -33,10 +33,7 @@ Body Parameters
 
 | Param            | Required                                  | Type     | Description                                                                      |
 | 
-
----
-
-------------- | ----------------------------------------- | -------- | -------------------------------------------------------------------------------- |
+| ---------------- | ----------------------------------------- | -------- | -------------------------------------------------------------------------------- |
 | nonce            | <span class="text-danger">REQUIRED</span> | `number` | The Nonce of the Sender.                                                         |
 | value            | <span class="text-danger">REQUIRED</span> | `string` | The Value to transfer, as a string representation of a Big Integer (can be "0"). |
 | receiver         | <span class="text-danger">REQUIRED</span> | `string` | The Address (bech32) of the Receiver.                                            |
@@ -269,7 +266,9 @@ _SimulationResults_
 | receipts | []ApiReceipt | an array of the receipts (if any) |
 | hash | string | the hash of the transaction |
 
-❕ Note that fields that are empty won't be included in the response. This can be seen in the examples below---
+❕ Note that fields that are empty won't be included in the response. This can be seen in the examples below
+
+---
 
 🟢 200: OK
 

docs/utils.mdx

@@ -42,6 +42,7 @@ _italicized text_
 `code`
 
 ### Horizontal Rule
+
 ---
 
 ### Link

docs/validators/key-management/validator-keys.md

@@ -20,8 +20,8 @@ The **Validator Keys** are located in the `validatorKey.pem` file, which is gene
 Below you can find their anatomy and how to extract the information from them
 
 Example:
----
---BEGIN PRIVATE KEY for _45e7131ba37e05c5de3f8862b4d8294812f004a5b660abb793e89b65816dbff2b02f54c25f139359c9c98be0fa657d0bf1ae4115dcf6fdbf5f3a470f1d251f769610b48fe34eeab59e82ac1cc0336d1d9109a14b768b97ccb4db4c2431629688_-----
+
+-----BEGIN PRIVATE KEY for _45e7131ba37e05c5de3f8862b4d8294812f004a5b660abb793e89b65816dbff2b02f54c25f139359c9c98be0fa657d0bf1ae4115dcf6fdbf5f3a470f1d251f769610b48fe34eeab59e82ac1cc0336d1d9109a14b768b97ccb4db4c2431629688_-----
 
 **YmRiNmViOGYzMmQ3OWY0YjE4ODJjMzE1ODA4YjQyZmZjODhiZDQxNzMwNmE5MTRiZjQ4OTAyNjM0MTcyNjMzMw==**