Merge pull request #3058 from federiconardelli7/federiconardelli7/small-issues-fix

Federiconardelli7/small issues fix

Author: ashucoder9

content/academy/permissioned-l1s/01-introduction/02-multi-chain-review.mdx

@@ -15,7 +15,7 @@ It's important to understand that a **Subnet or L1** is a validator set, while a
 
 While technically one Subnet can validate multiple chains (like the Primary Network validating P-Chain, C-Chain, and X-Chain), **in production it's almost always a 1:1 relationship**, and we strongly recommend keeping it as such for:
 - **Simpler management**
-- **Resource isolation**: Each application gets dedicated validator resources, and in the scenario that multiple validators go done, at least only one chain will be affected.  
+- **Resource isolation**: Each application gets dedicated validator resources, and in the scenario that multiple validators go down, at least only one chain will be affected.  
 
 ## Subnets
 

content/common/primary-network/p-chain.mdx

@@ -1,6 +1,6 @@
 In the Avalanche Network, the P-Chain of the Primary Network is responsible for all validator and Avalanche L1-level operations. The P-Chain supports the creation of new blockchains and Avalanche L1s, the addition of validators to Avalanche L1s, staking operations, and other platform-level operations. 
 
-![P-Chain](/common-images/primary-network/p-chain.png)
+<img src="/common-images/primary-network/p-chain.png" alt="P-Chain" />
 
 Each Avalanche validator can register a BLS public key alongside its NodeID on the Avalanche P-Chain. Validators of Avalanche L1s can stake different amounts of the Avalanche L1's staking token. Through the P-Chain, we can determine a weighted set of BLS Public Keys that correspond to the validators of each Avalanche L1 on the Avalanche Network.