Merge branch 'development' of github.com:multiversx/mx-docs into upda…

…te-build-flow

.github/workflows/deploy-staging.yml

@@ -2,7 +2,7 @@ name: deploy-staging
 
 on:
   push:
-    branches: [development]
+    branches: [update-build-flow]
   repository_dispatch:
     types: deploy-staging
   workflow_dispatch:
@@ -13,7 +13,7 @@ jobs:
     steps:
       - uses: actions/checkout@v2
         with:
-          ref: development
+          ref: update-build-flow
           fetch-depth: 0
       - name: Use Node.js
         uses: actions/setup-node@v1

docs/developers/meta/interactor/interactors-example.md

@@ -89,8 +89,7 @@ Following this command, the `state.toml` file becomes visible and contains the n
 
 ### Attach tracer (optional)
 
-Optionally, let's attach a [tracer](/developers/interactor/interactors-overview#traces) to the interactor. This records every action and writes it as a mandos step at a specified path.
-
+Optionally, let's attach a [tracer](/developers/meta/interactor/interactors-overview#traces) to the interactor. This records every action and writes it as a mandos step at a specified path.
 
 ```rust title=interactor_main.rs
 impl ContractInteract {

docs/developers/tutorials/crowdfunding-p1.md

@@ -212,7 +212,7 @@ It's time to add some functionality to the `init` function now, because the next
 
 [comment]: # (mx-context-auto)
 
-# **Step 4: the test**
+## **Step 4: the test**
 
 In this step you will use the `init` method to persist some values in the storage of the Crowdfunding smart contract. Afterwards, we will write a test to make sure that these values were properly stored.
 

docs/integrators/faq.md

@@ -40,7 +40,7 @@ Integrators may choose to have a unified view of the network, leveraging the [hy
 
 ### What signature scheme does MultiversX use?
 
-For transactions, [ed25519](/developers/signing-transactions/signing-transactions) is used.
+For transactions, [ed25519](/developers/signing-transactions) is used.
 
 ### What BIP-0044 coin type is being used?
 
@@ -87,8 +87,9 @@ Regular user accounts get created on the blockchain when the corresponding addre
 ### How to distinguish between a normal account and a smart contract?
 
 Examples of addresses:
- - **regular user account:** `erd1qyu5wthldzr8wx5c9ucg8kjagg0jfs53s8nr3zpz3hypefsdd8ssycr6th`
- - **smart contract:** `erd1qqqqqqqqqqqqqpgqq66xk9gfr4esuhem3jru86wg5hvp33a62jps2fy57p`
+
+- **regular user account:** `erd1qyu5wthldzr8wx5c9ucg8kjagg0jfs53s8nr3zpz3hypefsdd8ssycr6th`
+- **smart contract:** `erd1qqqqqqqqqqqqqpgqq66xk9gfr4esuhem3jru86wg5hvp33a62jps2fy57p`
 
 If the address (decoded as bytes) has a prefix of 8 bytes of `0x00`, then it refers to a smart contract.
 
@@ -103,4 +104,3 @@ Look for events of type [`SCDeploy`](/developers/event-logs/contract-deploy-even
 ### Is it possible to upgrade a smart contract?
 
 Yes, if the `upgradeable` flag is set in the contract's [metadata](/developers/data/code-metadata). Also see [upgrading smart contracts](/developers/developer-reference/upgrading-smart-contracts).
-

docs/tokens/nft-tokens.mdx

@@ -6,6 +6,7 @@ title: NFT & SFT tokens
 ```mdx-code-block
 import Tabs from "@theme/Tabs";
 import TabItem from "@theme/TabItem";
+import TableWrapper from "@site/src/components/TableWrapper";
 ```
 
 [comment]: # (mx-context-auto)
@@ -428,6 +429,7 @@ Below you can find a table with the supported media types for NFTs available on
 
 Below you can find a table representing an example of the fields for a non-fungible token that resembles a song.
 
+<TableWrapper>
 | Property       | Plain value                                            | Encoded value                                                                                            |
 |----------------|--------------------------------------------------------|----------------------------------------------------------------------------------------------------------|
 | **NFT Name**   | Beautiful song                                         | 42656175746966756c20736f6e67                                                                             |
@@ -436,6 +438,7 @@ Below you can find a table representing an example of the fields for a non-fungi
 | **Hash**       | 00                                                     | 00                                                                                                       |
 | **Attributes** | metadata:_ipfsCID/song.json_;tags:song,beautiful,music | 6d657461646174613a697066734349442f736f6e672e6a736f6e3b746167733a736f6e672c62656175746966756c2c6d75736963 |
 | **URI**        | _URL_to_decentralized_storage/song.mp3_                | 55524c5f746f5f646563656e7472616c697a65645f73746f726167652f736f6e672e6d7033                               |
+</TableWrapper>
 
 In this example we are creating a NFT represeting a song. Hash is left null, we are sharing media location URL and we are also providing the location of the extra metadata within the attributes field.