diff --git a/docs/learn/learn-guides-accounts.md b/docs/learn/learn-guides-accounts.md
index 0635ea671477..cf72c7caac21 100644
--- a/docs/learn/learn-guides-accounts.md
+++ b/docs/learn/learn-guides-accounts.md
@@ -18,14 +18,14 @@ description: Comprehensive guides for managing accounts, backups, and security u
 
 ## Account Address Format
 
-An account created on the relay chain can also be used on multiple chains in the ecosystem. More
+An account created on Polkadot can also be used on multiple chains in the ecosystem. More
 specifically, the account of a chain that uses the `*25519` account address format (the latest list
 can be accessed on the
 [ss58 registry repository](https://github.com/paritytech/ss58-registry/blob/main/ss58-registry.json))
 is cross-compatible with all the chains that use the similar format. To switch between the accounts
 on different chains, you can follow the guidelines in
 [this support article](https://support.polkadot.network/support/solutions/articles/65000103707-can-i-use-the-same-account-on-polkadot-kusama-and-parachains-).
-[Subscan has a tool](https://polkadot.subscan.io/tools/format_transform) you can use to convert your
+[Subscan has a tool](https://assethub-polkadot.subscan.io/tools/format_transform) you can use to convert your
 address between the different chain formats.
 
 !!!info "Using the same account on multiple chains - Pros and Cons"
diff --git a/docs/learn/learn-guides-treasury.md b/docs/learn/learn-guides-treasury.md
index 9220f9f51f45..1dd50c16c1d9 100644
--- a/docs/learn/learn-guides-treasury.md
+++ b/docs/learn/learn-guides-treasury.md
@@ -43,7 +43,7 @@ proposer.
 ## Creating a Treasury Proposal - Spend Local
 
 !!!info ""Spend" vs. "Spend Local""
-    You may notice that the Treasury pallet contains two extrinsics - `treasury.spend` and `treasury.spendLocal`. `treasury.spendLocal` (formally called `treasury.spend`) refers to a spend of DOT that is locally available, i.e., DOT from the relay chain's treasury account. `spend` actually allows the caller to specify an asset other than DOT, or even assets in other locations, e.g. [Asset Hub](../general/glossary.md#asset-hub).
+    You may notice that the Treasury pallet contains two extrinsics - `treasury.spend` and `treasury.spendLocal`. `treasury.spendLocal` (formally called `treasury.spend`) refers to a spend of DOT that is locally available, i.e., DOT from the Asset Hub treasury account. `spend` actually allows the caller to specify an asset other than DOT, or even assets in other locations, e.g. [Asset Hub](../general/glossary.md#asset-hub).
 
 Unlike `treasury.spendLocal`, `treasury.spend` is **not** bound by a spend period, and must be
 claimed manually via the `treasury.payout` extrinsic. `treasuy.spendLocal` behavior remains
@@ -173,9 +173,9 @@ Now, let's go through each field one-by-one and fill them in accordingly:
 - The relative location of the asset, and
 - How it is identified within this location.
 
-For this example, we are using USDT, which from the perspective of the relay chain would be:
+For this example, we are using USDT, which from the perspective of the Asset Hub would be:
 
-`Parachain 1000 (AssetHub) > AssetId (Concrete) > PalletInstance 50 > General Index 1984`
+`AssetId (Concrete) > PalletInstance 50 > General Index 1984`
 
 First, we specify the location - in this case, Asset Hub (parachain 1,000). `PalletInstance 50`
 refers to the Assets pallet instance on Asset Hub. The general index is `1984`, which is the ID of
@@ -210,7 +210,7 @@ an account address on the chain.
 
 ### Specifying `validFrom` (optional)
 
-The `validFrom` field is optional, and refers to the block height of the relay chain upon which the
+The `validFrom` field is optional, and refers to the block height of the Asset Hub upon which the
 payout can be issued. If the `validFrom` parameter is not set, the spend can be [claimed](#manually-claiming-payouts) immediately
 after approval. For more information on this field, refer to the
 [guide below](#creating-a-multistage-payout-proposal-with-validfrom).