Merge pull request #852 from multiversx/development

Development into main

docs/developers/tutorials/your-first-dapp.md

@@ -157,13 +157,15 @@ We'll take a look at the log output. We have 2 elements that need our attention:
 
 Devnet Explorer will be your best friend in developing dApps on the MultiversX Blockchain, as you'll first deploy and test your dApps on Devnet.
 
+```sh
 INFO:accounts:Account.sync_nonce()
 INFO:accounts:Account.sync_nonce() done: 32
 INFO:cli.contracts:Contract address: erd1qqqqqqqqqqqqqpgq0hmfvuygs34cgqsvgg6fpq9c5mffh4y04cysagr6cn
 INFO:utils:View this contract address in the MultiversX Devnet Explorer: https://devnet-explorer.multiversx.com/accounts/erd1qqqqqqqqqqqqqpgq0hmfvuygs34cgqsvgg6fpq9c5mffh4y04cysagr6cn
 INFO:transactions:Transaction.send: nonce=32
 INFO:transactions:Hash: ee84f3e833d439e159c9619fd76e26d2afcdad62c197d87e4940072f18558153
 INFO:utils:View this transaction in the MultiversX Devnet Explorer: https://devnet-explorer.multiversx.com/transactions/ee84f3e833d439e159c9619fd76e26d2afcdad62c197d87e4940072f18558153
+```
 
 The smart contract is now deployed on the blockchain. We can interact with it using blockchain transactions in order to invoke smart contract functions `ping` or `pong`.
 

docs/integrators/snapshotless-observing-squad.md

@@ -86,3 +86,8 @@ Failure to do so will make the node error with a message like `consensusComponen
 ### One click deploy in AWS
 AWS instances for Snapshotless Observing Squads can be easily deployed via our Amazon Machine Image available in the [AWS Marketplace](https://aws.amazon.com/marketplace/pp/prodview-pbwpmtdtwmkgs).
 
+[comment]: # (mx-context-auto)
+
+### One click deploy in Google Cloud
+Google Cloud instances for Snapshotless Observing Squads can be easily deployed via our virtual magine image available in the [Google Cloud Marketplace](https://console.cloud.google.com/marketplace/product/multiversx-gcp-markeplace/multiversx-snapshotless-observing-squad).
+

docs/sdk-and-tools/indices/accountsesdt.md

@@ -11,7 +11,7 @@ This page describes the structure of the `accounts-esdt` index (Elasticsearch),
 
 ## _id
 
-The `_id` field of this index is composed in this way: `{bech32address}_{tokenIdentifier}_{nonce}` (example: `erd.._abcd-0123-01`).
+The `_id` field of this index is composed in this way: `{bech32address}-{tokenIdentifier}-{nonce}` (example: `erd..-abcd-0123-01`).
 
 [comment]: # (mx-context-auto)
 

docs/sdk-and-tools/sdk-js/extending-sdk-js.md

@@ -1,6 +1,7 @@
 ---
 id: extending-sdk-js
 title: Extending sdk-js
+pagination_prev: sdk-and-tools/sdk-js/sdk-js
 ---
 
 [comment]: # (mx-abstract)

docs/sdk-and-tools/sdk-js/sdk-js-cookbook.md → docs/sdk-and-tools/sdk-js/sdk-js-cookbook-v12.md

@@ -1,14 +1,15 @@
 ---
-id: sdk-js-cookbook
-title: Cookbook
+id: sdk-js-cookbook-v12
+title: Cookbook (v12)
+pagination_next: sdk-and-tools/sdk-js/extending-sdk-js
 ---
 
 [comment]: # (mx-abstract)
 
 This page will guide you through the process of handling common tasks using **sdk-js**.
 
 :::important
-This cookbook makes use of `sdk-js 12`. In order to migrate from `sdk-js 11.x` to `sdk-js 12`, please follow [the migration guide](/sdk-and-tools/sdk-js/sdk-js-migration-guides).
+This cookbook makes use of `sdk-js v12`. In order to migrate from `sdk-js v11.x` to `sdk-js v12`, please follow [the migration guide](/sdk-and-tools/sdk-js/sdk-js-migration-guides).
 :::
 
 <!-- BEGIN_INCLUDE_FILE { "url": "https://raw.githubusercontent.com/multiversx/mx-sdk-js-examples/v0.6.0/cookbook/generated/basic.md" } -->