Update sdk-py documentation

docs/developers/relayed-transactions.md

@@ -115,6 +115,6 @@ Here's an example of a relayed v3 transaction. Its intent is to call the `add` m
 
 The SDKs have built-in support for relayed transactions. Please follow:
  - [mxpy support](/sdk-and-tools/mxpy/mxpy-cli/#relayed-transactions-v3)
- - [sdk-py support](/sdk-and-tools/sdk-py/sdk-py-cookbook/#relayed-transactions)
+ - [sdk-py support](/sdk-and-tools/sdk-py/#relayed-transactions)
  - [sdk-js v14 support](/sdk-and-tools/sdk-js/sdk-js-cookbook#relayed-transactions)
  - [sdk-js v13 support (legacy)](/sdk-and-tools/sdk-js/sdk-js-cookbook-v13#preparing-a-relayed-transaction)

docs/developers/signing-transactions/signing-programmatically.md

@@ -6,4 +6,4 @@ title: Signing programmatically
 In order to sign a transaction (or a message) using one of the SDKs, follow:
 
 - [Signing objects using **sdk-js**](/sdk-and-tools/sdk-js/sdk-js-cookbook#signing-objects)
-- [Signing objects using **sdk-py**](/sdk-and-tools/sdk-py/sdk-py-cookbook#signing-objects)
+- [Signing objects using **sdk-py**](/sdk-and-tools/sdk-py#signing-objects)

docs/sdk-and-tools/sdk-js/writing-and-running-sdk-js-snippets.md

@@ -7,6 +7,6 @@ title: Writing and testing interactions
 
 Generally speaking, we recommended to use [sc-meta CLI](/developers/meta/sc-meta-cli) to [generate the boilerplate code for your contract interactions](/developers/meta/sc-meta-cli/#calling-snippets).
 
-Though, for writing contract interaction snippets in **JavaScript** or **TypeScript**, please refer to the [`sdk-js` cookbook](/sdk-and-tools/sdk-js/sdk-js-cookbook). If you'd like these snippets to function as system tests of your contract, a choice would be to structure them as Mocha or Jest tests - take the `*.local.net.spec.ts` tests in [`mx-sdk-js-core`](https://github.com/multiversx/mx-sdk-js-core) as examples. For writing contract interaction snippets in **Python**, please refer to the [`sdk-py` cookbook](/sdk-and-tools/sdk-py/sdk-py-cookbook) - if desired, you can shape them as simple scripts, as Python unit tests, or as Jupyter notebooks.
+Though, for writing contract interaction snippets in **JavaScript** or **TypeScript**, please refer to the [`sdk-js` cookbook](/sdk-and-tools/sdk-js/sdk-js-cookbook). If you'd like these snippets to function as system tests of your contract, a choice would be to structure them as Mocha or Jest tests - take the `*.local.net.spec.ts` tests in [`mx-sdk-js-core`](https://github.com/multiversx/mx-sdk-js-core) as examples. For writing contract interaction snippets in **Python**, please refer to the [`sdk-py` cookbook](/sdk-and-tools/sdk-py) - if desired, you can shape them as simple scripts, as Python unit tests, or as Jupyter notebooks.
 
 You might also want to have a look over [**xSuite**](https://xsuite.dev), a toolkit to init, build, test, deploy contracts using JavaScript, made by the [Arda team](https://arda.run).

docs/sdk-and-tools/sdk-py/sdk-py-cookbook-v1.md → docs/sdk-and-tools/sdk-py.md

@@ -1,7 +1,7 @@
 ---
-id: sdk-py-cookbook
-title: Cookbook (v1)
-pagination_prev: sdk-and-tools/sdk-py/sdk-py-cookbook-v0
+id: sdk-py
+title: Python SDK
+pagination_prev: developers/testing/testing-in-go
 pagination_next: sdk-and-tools/mxpy/installing-mxpy
 ---