feat: Rebrand Kurdistan SDK to PezkuwiChain

bizinikiwi/docs/Upgrading-2.0-to-3.0.md

@@ -309,9 +309,9 @@ adequate deposit associated with them. A number of configuration parameters has
  ```
 
  **This upgrade requires storage
- [migration](https://github.com/paritytech/bizinikiwi/blob/master/frame/elections-phragmen/src/migrations_3_0_0.rs)**.
+ [migration](https://github.com/pezkuwichain/kurdistan-sdk/blob/main/bizinikiwi/pezframe/elections-phragmen/src/migrations_3_0_0.rs)**.
  Further details can be found in the [pezpallet-specific
- changelog](https://github.com/paritytech/bizinikiwi/blob/master/frame/elections-phragmen/CHANGELOG.md#security).
+ changelog](https://github.com/pezkuwichain/kurdistan-sdk/blob/main/bizinikiwi/pezframe/elections-phragmen/CHANGELOG.md#security).
 
 #### (changes) Democracy
 
@@ -360,15 +360,15 @@ are effected by changes and how to update your code yourself.
 A few minor things have changed in the `cli` (compared to 2.0.1):
 
 1. we've [replaced the newly added `BuildSyncSpec` subcommand with an RPC
-   API](https://github.com/paritytech/bizinikiwi/commit/65cc9af9b8df8d36928f6144ee7474cefbd70454#diff-c57da6fbeff8c46ce15f55ea42fedaa5a4684d79578006ce4af01ae04fd6b8f8)
+   API](https://github.com/pezkuwichain/kurdistan-sdk/commit/65cc9af9b8df8d36928f6144ee7474cefbd70454#diff-c57da6fbeff8c46ce15f55ea42fedaa5a4684d79578006ce4af01ae04fd6b8f8)
    in an on-going effort to make light-client-support smoother, see below
 2. we've [removed double accounts from our
-   chainspec-builder](https://github.com/paritytech/bizinikiwi/commit/31499cd29ed30df932fb71b7459796f7160d0272)
+   chainspec-builder](https://github.com/pezkuwichain/kurdistan-sdk/commit/31499cd29ed30df932fb71b7459796f7160d0272)
 3. we [don't fallback to `--chain flaming-fir`
-   anymore](https://github.com/paritytech/bizinikiwi/commit/13cdf1c8cd2ee62d411f82b64dc7eba860c9c6c6), if no chain is
+   anymore](https://github.com/pezkuwichain/kurdistan-sdk/commit/13cdf1c8cd2ee62d411f82b64dc7eba860c9c6c6), if no chain is
    given our `bizinikiwi-node` will error.
 4. [the `subkey`-integration has seen a fix to the
-   `insert`-command](https://github.com/paritytech/bizinikiwi/commit/54bde60cfd2c544c54e9e8623b6b8725b99557f8) that
+   `insert`-command](https://github.com/pezkuwichain/kurdistan-sdk/commit/54bde60cfd2c544c54e9e8623b6b8725b99557f8) that
    requires you to now add the `&cli` as a param.
     ```diff=
     --- a/bin/node/cli/src/command.rs

bizinikiwi/docs/node-template-release.md

@@ -26,7 +26,7 @@ that are removed from the source. So you need to manually check and remove them
 commit in Bizinikiwi remote repository, such as:
 
 ```toml
-toml pezsp-core = { version = "7.0.0", git = "https://github.com/paritytech/bizinikiwi.git", rev =
+toml pezsp-core = { version = "7.0.0", git = "https://github.com/pezkuwichain/kurdistan-sdk.git", rev =
 "de80d0107336a9c7a2efdc0199015e4d67fcbdb5", default-features = false }
 ```
 

bizinikiwi/docs/rustdocs-release.md

@@ -2,7 +2,7 @@
 
 There is [a script in place](../.maintain/rustdocs-release.sh) to manage the deployment of Bizinikiwi rustdocs at
 https://docs.pezkuwichain.io/bizinikiwi, which is pushing the rustdocs file in `gh-pages` branch of
-https://github.com/paritytech/bizinikiwi.
+https://github.com/pezkuwichain/kurdistan-sdk.
 
 The documentation at the top of the `rustdocs-release.sh` explains most of the mechanics of the script.