nitpix

Author: MichaelTrestman

docs/keys/proxies/create-proxy.md

@@ -50,7 +50,7 @@ If the web app does not connect to your local chain, your browser’s privacy or
 4. Fill the parameters:
 
    - `delegate`: select the imported delegate account from the _Accounts_ dropdown.
-   - `proxyType`: select `SmallTransfer`; this should allow us transfer amounts that do not exceed 0.5τ.
+   - `proxyType`: select `SmallTransfer`; this should allow us to transfer amounts that do not exceed 0.5τ.
    - `delay`: optionally, include a delay in blocks.
 
 5. Click **Submit Transaction** and sign with the _delegator_ account.
@@ -155,7 +155,7 @@ After the announcement waiting period has passed, the delegate account can now e
 
 :::info
 
-- The call details must exactly match the original announcement. Any change—such as modifying the recipient or amount—will result in a `proxy.Unannounced error.
+- The call details must exactly match the original announcement. Any change—such as modifying the recipient or amount—will result in a `proxy.Unannounced` error.
 - Once a delayed proxy call is executed, its announcement is cleared. To run another proxy with the same details, you must create a new announcement.
   :::
 
@@ -167,11 +167,11 @@ After the announcement waiting period has passed, the delegate account can now e
 
 1. In the navbar menu, navigate to **Developers** → **Extrinsics**.
 2. Under “using the selected account”, pick the delegator account.
-3. Under “submit the following extrinsic”, choose the `proxy` pallete and call `removeProxy(delegate, proxyType, delay)`.
+3. Under "submit the following extrinsic", choose the `proxy` pallet and call `removeProxy(delegate, proxyType, delay)`.
 4. Fill the parameters:
 
    - `delegate`: select the imported delegate account from the _Accounts_ dropdown.
-   - `proxyType`: select `SmallTransfer`; this should allow us transfer amounts that do not exceed 0.5τ.
+   - `proxyType`: select `SmallTransfer`; this should allow us to transfer amounts that do not exceed 0.5τ.
    - `delay`: Optionally, include a delay in blocks.
 
 5. Click **Submit Transaction** and sign with the _delegator_ account.

docs/keys/proxies/index.md

@@ -9,7 +9,7 @@ This page introduces the proxy pattern used in Bittensor and explains how it ena
 Rather than using funds in a single account, accounts with unique roles can complete tasks on behalf of the main stash account.
 A proxy lets one account (the delegator, or "real" account) authorize another account (the delegate) to make permitted calls on its behalf. Proxies allow a delegator to keep their "real" accounts safe and "cold", thereby adding an extra layer of security to the tokens in the account.
 
-The permission scope is determined by the `ProxyType` call filter. This call filter allows the delegator account set the roles and limitations of the delegate account. Optionally, actions can require an on-chain announcement period—`delay`, giving the delegator time to reject a call made by a delegate.
+The permission scope is determined by the `ProxyType` call filter. This call filter allows the delegator account to set the roles and limitations of the delegate account. Optionally, actions can require an on-chain announcement period—`delay`, giving the delegator time to reject a call made by a delegate.
 
 ## Proxy terminology
 

docs/keys/proxies/pure-proxies.md

@@ -14,7 +14,7 @@ Pure proxies are **keyless, non-deterministic accounts** that are created fresh
 
 Unlike standard proxies, where the delegate can access the delegator’s funds to execute calls on their behalf, pure proxies operate differently. A pure proxy account must hold its own funds, while the real account acts as an _any proxy_ for it—signing and authorizing transactions on the proxy’s behalf.
 
-:::info when to use pure proxies
+:::info When to use pure proxies
 Pure proxies are valuable when you want to keep your real account secure by reducing direct key exposure to the blockchain. They provide a keyless, flexible account that enables permissionless management and are especially effective for multisigs, since they allow updates to membership or thresholds without changing the account address.
 :::
 
@@ -98,7 +98,7 @@ Pure proxies are killed using the `killPure` extrinsic as shown. See [source cod
 2. Under “using the selected account”, choose the pure proxy account.
 3. Select the `proxy` pallet and choose `killPure(spawner, proxyType, index, height, extIndex)`.
 4. Fill the parameters:
-   - `spawner`: select the account that created the proxy from th UI.
+   - `spawner`: select the account that created the proxy from the UI.
    - `proxyType`: select the proxy type.
    - `index`: leave as `0`.
    - `height`: input the block number that the proxy was created at.
@@ -113,7 +113,7 @@ Killing a pure proxy permanently deletes the account and releases its reserved d
 
 ## Troubleshooting
 
-- `Token.FundsUnavailable`: Ensure thhat the pure proxy account has been funded and has enough funds to cover the transfer.
+- `Token.FundsUnavailable`: Ensure that the pure proxy account has been funded and has enough funds to cover the transfer.
 - `proxy.NotProxy`: Ensure you're executing the pure proxy correctly—from the creator account and referencing the pure proxy account as `real`. See [source code: `NotProxy` error](https://github.com/opentensor/subtensor/blob/main/pallets/proxy/src/lib.rs#L735).
 - `Proxy.NoPermission`: The `killPure` call is not permitted under the current. See [source code: `NoPermission` error](https://github.com/opentensor/subtensor/blob/main/pallets/proxy/src/lib.rs#L741).
 - `system.CallFiltered`: The call is not permitted under the current `ProxyType`.