refactor: proposal api links

docs/src/implemented-proposals/rpc-transaction-history.md

@@ -10,13 +10,13 @@ fall back to the external data store.
 
 The affected RPC endpoints are:
 
-- [getFirstAvailableBlock](developing/clients/jsonrpc-api.md#getfirstavailableblock)
-- [getConfirmedBlock](developing/clients/jsonrpc-api.md#getconfirmedblock)
-- [getConfirmedBlocks](developing/clients/jsonrpc-api.md#getconfirmedblocks)
-- [getConfirmedSignaturesForAddress](developing/clients/jsonrpc-api.md#getconfirmedsignaturesforaddress)
-- [getConfirmedTransaction](developing/clients/jsonrpc-api.md#getconfirmedtransaction)
-- [getSignatureStatuses](developing/clients/jsonrpc-api.md#getsignaturestatuses)
-- [getBlockTime](developing/clients/jsonrpc-api.md#getblocktime)
+- [getFirstAvailableBlock](../api/http#getfirstavailableblock)
+- [getConfirmedBlock](../api/http#getconfirmedblock)
+- [getConfirmedBlocks](../api/http#getconfirmedblocks)
+- [getConfirmedSignaturesForAddress](../api/http#getconfirmedsignaturesforaddress)
+- [getConfirmedTransaction](../api/http#getconfirmedtransaction)
+- [getSignatureStatuses](../api/http#getsignaturestatuses)
+- [getBlockTime](../api/http#getblocktime)
 
 Some system design constraints:
 

docs/src/implemented-proposals/transaction-fees.md

@@ -6,14 +6,14 @@ title: Deterministic Transaction Fees
 
 Before sending a transaction to the cluster, a client may query the network to
 determine what the transaction's fee will be via the rpc request
-[getFeeForMessage](/developing/clients/jsonrpc-api#getfeeformessage).
+[getFeeForMessage](../api/http#getfeeformessage).
 
 ## Fee Parameters
 
 The fee is based on the number of signatures in the transaction, the more
 signatures a transaction contains, the higher the fee. In addition, a
 transaction can specify an additional fee that determines how the transaction is
-relatively prioritized against others.  A transaction's prioritization fee is
+relatively prioritized against others. A transaction's prioritization fee is
 calculated by multiplying the number of compute units by the compute unit price
 (measured in micro-lamports) set by the transaction via compute budget
 instructions.