Fix source links + clarify transaction fee and owner reserve.

Author: maria-robobug

docs/xls-65d-single-asset-vault/concepts/pseudo-account.md

@@ -26,7 +26,7 @@ A pseudo-account has strict limitations. It cannot receive payments from other a
 
 The cost of creating a pseudo-account depends on whether it is owned and controlled by another account:
 
-- **Owned pseudo-accounts**: For objects like a `Vault` where a single account owns and controls the associated pseudo-account, the creation transaction increases the owner's XRP reserve by one [incremental owner reserve](https://xrpl.org/docs/concepts/accounts/reserves#base-reserve-and-owner-reserve) (currently 0.2 XRP). This is in addition to any other reserve requirements of the transaction (for example, the Vault object itself). The transaction fee is the standard network fee.
+- **Owned pseudo-accounts**: For objects like a `Vault` where a single account owns and controls the associated pseudo-account, the creation transaction increases the owner's XRP reserve by one [incremental owner reserve](https://xrpl.org/docs/concepts/accounts/reserves#base-reserve-and-owner-reserve) (currently 0.2 XRP). This is in addition to any other reserve requirements of the transaction (for example, the Vault object itself).
 
 - **Unowned pseudo-accounts**: For objects like an `AMM` that are not owned by any account, the creation transaction charges a special, higher-than-normal transaction fee. This fee must be at least the value of one incremental owner reserve. This amount is burned, compensating for the permanent ledger space without tying the reserve to a specific owner.
 

docs/xls-65d-single-asset-vault/reference/api/vault-info.md

@@ -7,7 +7,7 @@ labels:
 
 # vault_info
 
-[[Source]](https://github.com/XRPLF/rippled/blob/develop/src/xrpld/rpc/handlers/VaultInfo.cpp "Source")<br/>
+[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/rpc/handlers/VaultInfo.cpp "Source")<br/>
 
 The `vault_info` command retrieves information about a vault, its owner, available assets, and details on issued shares. All information retrieved is relative to a particular version of the ledger.
 

docs/xls-65d-single-asset-vault/reference/transactions/vaultclawback.md

@@ -8,7 +8,7 @@ labels:
 
 # VaultClawback
 
-[[Source]](https://github.com/Bronek/rippled/blob/vault/src/xrpld/app/tx/detail/VaultClawback.cpp "Source")
+[[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/VaultClawback.cpp "Source")
 
 Performs a [Clawback](https://xrpl.org/docs/use-cases/tokenization/stablecoin-issuer#clawback) from the vault, exchanging the shares of an account for assets.
 

docs/xls-65d-single-asset-vault/reference/transactions/vaultcreate.md

@@ -74,7 +74,7 @@ A `WithdrawalPolicy` defines the strategy for processing withdrawal requests fro
 
 ## Transaction Cost
 
-Since the {% code-page-name /%} transaction creates a new `AccountRoot` object for a vault’s pseudo-account, it incurs a higher than usual [transaction cost](https://xrpl.org/docs/concepts/transactions/transaction-cost) to deter ledger spam. Instead of the standard minimum of 0.00001 XRP, {% code-page-name /%} must destroy an [incremental owner reserve](https://xrpl.org/docs/concepts/accounts/reserves#base-reserve-and-owner-reserve), currently 0.2 XRP. This reserve is returned to the owner when the vault is deleted.
+Since the {% code-page-name /%} transaction creates a new `AccountRoot` object for a vault’s pseudo-account, it incurs a higher than usual [transaction cost](https://xrpl.org/docs/concepts/transactions/transaction-cost) to deter ledger spam. Instead of the standard minimum of 0.00001 XRP, {% code-page-name /%} must destroy an [incremental owner reserve](https://xrpl.org/docs/concepts/accounts/reserves#base-reserve-and-owner-reserve), currently 0.2 XRP.
 
 ## Error Cases
 

docs/xls-65d-single-asset-vault/reference/transactions/vaultdelete.md

@@ -10,7 +10,7 @@ labels:
 
 [[Source]](https://github.com/XRPLF/rippled/blob/master/src/xrpld/app/tx/detail/VaultDelete.cpp "Source")
 
-Permanently deletes an existing `Vault` object from the ledger, removes all associated ledger entries, and returns the owner reserve to the Vault Owner.
+Permanently deletes an existing `Vault` object from the ledger, removes all associated ledger entries, and frees up the reserve requirement for the Vault Owner.
 
 Only the Vault Owner can initiate this transaction, and the vault must be completely empty before deletion.