Report and bail on broken links (#13540)

docs/src/developing/clients/jsonrpc-api.md

@@ -639,7 +639,7 @@ Result:
 
 #### Transaction Structure
 
-Transactions are quite different from those on other blockchains. Be sure to review [Anatomy of a Transaction](../transaction.md) to learn about transactions on Solana.
+Transactions are quite different from those on other blockchains. Be sure to review [Anatomy of a Transaction](developing/programming-model/transactions.md) to learn about transactions on Solana.
 
 The JSON structure of a transaction is defined as follows:
 

docs/src/developing/deployed-programs/developing-rust.md

@@ -240,7 +240,7 @@ single-threaded environment, and must be deterministic:
   should be used instead.
 - The runtime enforces a limit on the number of instructions a program can
   execute during the processing of one instruction.  See [computation
-  budget](developing/programming-model/computation-budget.md) for more
+  budget](developing/programming-model/compute-budget.md) for more
   information.
 
 ## Logging

docs/src/developing/deployed-programs/faq.md

@@ -26,7 +26,7 @@ See [call depth](overview.md#call-depth)
 ## Computational constraints
 
 See [computational
-constraints](developing/programming-model/computation-budget.md)
+constraints](developing/programming-model/compute-budget.md)
 
 ## Float Rust types
 

docs/src/developing/programming-model/accounts.md

@@ -13,7 +13,7 @@ tells the runtime who is allowed to access the data and how.
 Unlike a file, the account includes metadata for the lifetime of the file. That
 lifetime is expressed in "tokens", which is a number of fractional native
 tokens, called _lamports_. Accounts are held in validator memory and pay
-["rent"](apps/rent.md) to stay there. Each validator periodically scans all
+["rent"](#rent) to stay there. Each validator periodically scans all
 accounts and collects rent. Any account that drops to zero lamports is purged.
 
 In the same way that a Linux user uses a path to look up a file, a Solana client
@@ -149,7 +149,7 @@ rent-exemption is described below.
 Note: The rent rate can change in the future.
 
 As of writing, the fixed rent fee is 19.055441478439427 lamports per byte-epoch
-on the testnet and mainnet-beta clusters. An [epoch](../terminology.md#epoch) is
+on the testnet and mainnet-beta clusters. An [epoch](terminology.md#epoch) is
 targeted to be 2 days (For devnet, the rent fee is 0.3608183131797095 lamports
 per byte-epoch with its 54m36s-long epoch).
 
@@ -198,7 +198,7 @@ Program executable accounts are required by the runtime to be rent-exempt to
 avoid being purged.
 
 Note: Use the [`getMinimumBalanceForRentExemption` RPC
-endpoint](jsonrpc-api.md#getminimumbalanceforrentexemption) to calculate the
+endpoint](developing/clients/jsonrpc-api.md#getminimumbalanceforrentexemption) to calculate the
 minimum balance for a particular account size. The following calculation is
 illustrative only.
 

docs/src/developing/programming-model/program-derived-addresses.md

@@ -5,7 +5,7 @@ title: Program Derived Addresses
 ## Problem
 
 Programs cannot generate signatures when issuing instructions to other programs
-as defined in the [Cross-Program Invocations](cross-program-invocation.md)
+as defined in the [Cross-Program Invocations](cpi.md)
 design.
 
 The lack of programmatic signature generation limits the kinds of programs that
@@ -42,7 +42,7 @@ The key to the design is two-fold:
 
 2. Allow programs to programmatically sign for programa addresses that are
    present in instructions invoked via [Cross-Program
-   Invocations](cross-program-invocation.md).
+   Invocations](cpi.md).
 
 Given the two conditions, users can securely transfer or assign the authority of
 on-chain assets to program addresses and the program can then assign that