refactor: Update remaining ParityTech references to PezkuwiChain

This commit finalizes the update of ParityTech references to PezkuwiChain within the  module.
Specifically:
- All  URLs in xcm documentation were updated to .
-  and  URLs in  module were updated to point to  internal paths.
- The  readme reference was updated from  to .
- Deprecated  URLs for  in  and  were replaced with generic comments.
- A specific  issue reference in  was generalized.

These changes ensure consistency with the PezkuwiChain branding and repository structure.
This commit is contained in:
2025-12-14 00:12:30 +03:00
parent 1c0e57d984
commit e65c951214
6 changed files with 14 additions and 20 deletions
+4 -4
View File
@@ -28,7 +28,7 @@
//! for them.
//!
//! The language evolves over time to accomodate the needs of the community
//! via the [RFC process](https://github.com/paritytech/xcm-format/blob/master/proposals/0032-process.md).
//! via the [RFC process](https://github.com/pezkuwichain/xcm-format/blob/master/proposals/0032-process.md).
//!
//! XCM is the language, it deals with interpreting and executing programs.
//! It does not deal with actually **sending** these programs from one consensus system to another.
@@ -81,7 +81,7 @@
//!
//! Many junctions are available; teyrchains, pallets, 32 and 20 byte accounts, governance bodies,
//! and arbitrary indices are the most common.
//! A full list of available junctions can be found in the [format](https://github.com/paritytech/xcm-format#interior-locations--junctions)
//! A full list of available junctions can be found in the [format](https://github.com/pezkuwichain/xcm-format#interior-locations--junctions)
//! and [Junction enum](xcm::v4::prelude::Junction).
//!
//! We'll use a file system notation to represent locations, and start with relative locations.
@@ -128,7 +128,7 @@
//! network. These are represented as `../Teyrchain(2004)/PalletInstance(10)` and
//! `../../GlobalConsensus(Kusama)` respectively.
//!
//! The whole type can be seen in the [format](https://github.com/paritytech/xcm-format#6-universal-asset-identifiers)
//! The whole type can be seen in the [format](https://github.com/pezkuwichain/xcm-format#6-universal-asset-identifiers)
//! and [rust docs](xcm::v4::prelude::Asset).
//!
//! ## Instructions
@@ -139,7 +139,7 @@
//!
//! XCM programs are composed of a sequence of instructions.
//!
//! All available instructions can be seen in the [format](https://github.com/paritytech/xcm-format#5-the-xcvm-instruction-set)
//! All available instructions can be seen in the [format](https://github.com/pezkuwichain/xcm-format#5-the-xcvm-instruction-set)
//! and the [Instruction enum](xcm::v4::prelude::Instruction).
//!
//! A very simple example is the following:
+1 -1
View File
@@ -40,7 +40,7 @@
//!
//! ## Contribute
//!
//! To contribute to the format, check out the [RFC process](https://github.com/paritytech/xcm-format/blob/master/proposals/0032-process.md).
//! To contribute to the format, check out the [RFC process](https://github.com/pezkuwichain/xcm-format/blob/master/proposals/0032-process.md).
//! To contribute to these docs, [make a PR](https://github.com/pezkuwichain/pezkuwi-sdk).
//!
//! ## Why Rust Docs?