[links] Update TS SDK links (#818)

Author: gregnazario

apps/nextra/pages/en/build/guides/aptos-keyless/federated-keyless/other.mdx

@@ -6,9 +6,9 @@ title: "FAQ"
 
 **What if I stop using my IAM for my application? What if I switch IAM providers?**
 
-- An account address depends on values of several variables that are specific to an IAM service, including `aud` (client ID) and `iss` (issuer).  If these values are changed, then a different address will be derived. 
-- If you want to switch IAM providers, you will need to develop an account migration flow, resulting in a key rotation from the account derived from the prior IAM provider to the account derived from the new IAM provider. 
-- We recommend allowing your users to add a secondary authentication method to their accounts (e.g., back-up private key) so that they can maintain access should the authentication path into their account via Federated Keyless be disrupted via a service provider change. In order to implement this, you need to do a key rotation to a multikey account. For relevant documentation see [key rotation](https://aptos.dev/en/build/guides/key-rotation) and [multikey SDK](https://aptos-labs.github.io/aptos-ts-sdk/@aptos-labs/ts-sdk-1.29.1/classes/MultiKeyAccount.html).
+- An account address depends on values of several variables that are specific to an IAM service, including `aud` (client ID) and `iss` (issuer).  If these values are changed, then a different address will be derived.
+- If you want to switch IAM providers, you will need to develop an account migration flow, resulting in a key rotation from the account derived from the prior IAM provider to the account derived from the new IAM provider.
+- We recommend allowing your users to add a secondary authentication method to their accounts (e.g., back-up private key) so that they can maintain access should the authentication path into their account via Federated Keyless be disrupted via a service provider change. In order to implement this, you need to do a key rotation to a multikey account. For relevant documentation see [key rotation](https://aptos.dev/en/build/guides/key-rotation) and [multikey SDK](https://aptos-labs.github.io/aptos-ts-sdk/@aptos-labs/ts-sdk-1.35.0/classes/MultiKeyAccount.html).
 
 **Does using an IAM cost money?**
 
@@ -20,4 +20,4 @@ title: "FAQ"
 
 **I use an open source IAM like Keycloak. Can I use Federated Keyless?**
 
-- Not today. Due to the trust placed in the IAM to have sufficient uptime and security standards, we have limited the accepted IAM set to the currently supported issuers. If you believe your provider should be included for consideration, please consider raising an AIP or contact us in the Keyless developers [telegram](https://t.me/+h5CN-W35yUFiYzkx). 
+- Not today. Due to the trust placed in the IAM to have sufficient uptime and security standards, we have limited the accepted IAM set to the currently supported issuers. If you believe your provider should be included for consideration, please consider raising an AIP or contact us in the Keyless developers [telegram](https://t.me/+h5CN-W35yUFiYzkx).

apps/nextra/pages/en/build/sdks/ts-sdk/building-transactions.mdx

@@ -10,7 +10,7 @@ import { Callout, Steps } from 'nextra/components';
 Transactions allow you to change on-chain data or trigger events. Generally, transactions follow 5 steps from building to executing on chain: building, simulating, signing, submitting, and waiting.
 
 <Callout type="info">
-For these examples, `aptos` is an instance of the [`Aptos`](https://aptos-labs.github.io/aptos-ts-sdk/@aptos-labs/ts-sdk-1.12.2/classes/Aptos.html) client object.
+For these examples, `aptos` is an instance of the [`Aptos`](https://aptos-labs.github.io/aptos-ts-sdk/@aptos-labs/ts-sdk-1.35.0/classes/Aptos.html) client object.
 </Callout>
 
 <Steps>
@@ -51,7 +51,7 @@ The SDK provides sensible defaults for these values if they are not specified ex
 
 ### Simulate (Optional)
 
-Every transaction on the Aptos chain has a gas fee associated with how much work the network machines have to do when executing the transaction. In order to estimate the cost associated with that, you can simulate transactions before committing them. 
+Every transaction on the Aptos chain has a gas fee associated with how much work the network machines have to do when executing the transaction. In order to estimate the cost associated with that, you can simulate transactions before committing them.
 
 <Callout type="info">
 This simulation only requires the `publicKey` of an account since it will not impact the actual state of the ledger.
@@ -93,7 +93,7 @@ const committedTransaction = await aptos.transaction.submit.simple({
 
 ### Wait
 
-Finally, you can wait for the result of the transaction by using [`aptos.waitForTransaction`](https://aptos-labs.github.io/aptos-ts-sdk/@aptos-labs/ts-sdk-1.12.2/classes/Aptos.html#waitForTransaction) and specifying the hash of the transaction you just submitted like so:
+Finally, you can wait for the result of the transaction by using [`aptos.waitForTransaction`](https://aptos-labs.github.io/aptos-ts-sdk/@aptos-labs/ts-sdk-1.35.0/classes/Aptos.html#waitForTransaction) and specifying the hash of the transaction you just submitted like so:
 
 ```ts filename="build-a-transaction.ts"
 // 5. Wait
@@ -134,7 +134,7 @@ async function example() {
     await aptos.fundAccount({
         accountAddress: alice.accountAddress,
         amount: 100_000_000,
-    });  
+    });
     await aptos.fundAccount({
         accountAddress: bob.accountAddress,
         amount: 100,

apps/nextra/pages/en/build/sdks/ts-sdk/fetch-data-via-sdk.mdx

@@ -7,7 +7,7 @@ import { Callout } from 'nextra/components'
 
 # Fetch Data via the TypeScript SDK
 
-You can use the `Aptos` client to get on-chain data using a variety of helper functions. Specifically, many of the functions listed in the reference docs [here](https://aptos-labs.github.io/aptos-ts-sdk/@aptos-labs/ts-sdk-1.12.2/classes/Aptos.html) that start with `get...` will retrieve data from on-chain.
+You can use the `Aptos` client to get on-chain data using a variety of helper functions. Specifically, many of the functions listed in the reference docs [here](https://aptos-labs.github.io/aptos-ts-sdk/@aptos-labs/ts-sdk-1.35.0/classes/Aptos.html) that start with `get...` will retrieve data from on-chain.
 
 Here’s an example showing how to fetch common data you may need in your application:
 
@@ -42,7 +42,7 @@ The `Aptos` client can out of the box query both network data from [fullnodes](h
 
 ## Using Generic Queries
 
-Some queries are intentionally broad, but this can make inferring the proper return type difficult. To accommodate that, these broad requests like `getAccountResources` allow you to specify what the expected response type should be. 
+Some queries are intentionally broad, but this can make inferring the proper return type difficult. To accommodate that, these broad requests like `getAccountResources` allow you to specify what the expected response type should be.
 
 ```ts filename="fetch-data.ts"
 type Coin = { coin: { value: string } };
@@ -58,7 +58,7 @@ const value = resource.coin.value;
 
 ## Using Move View Functions
 
-You can call view functions which return custom data from on-chain by using `aptos.view`. 
+You can call view functions which return custom data from on-chain by using `aptos.view`.
 
 For example, you can look up the network you are using with the `chain_id` view function:
 
@@ -74,7 +74,7 @@ const chainId = (await aptos.view({ payload }))[0];
 
 Behind the scenes, some requests use the [Indexer API](../../indexer.mdx) to access data which has been processed or aggregated. That extra parsing can take a bit of time, so the data may lag slightly behind the latest ledger.
 
-If you want to ensure that the data is fresh, you can specify the `minimumLedgerVersion` in any request which uses the Indexer API. 
+If you want to ensure that the data is fresh, you can specify the `minimumLedgerVersion` in any request which uses the Indexer API.
 
 ```ts filename="fetch-data.ts"
 // Get the latest ledger version number
@@ -86,7 +86,7 @@ const tokens = await aptos.getAccountOwnedTokens({
 });
 ```
 
-You can also ensure that your request has the data from a transaction you submitted by getting the ledger version from the transaction validation itself. 
+You can also ensure that your request has the data from a transaction you submitted by getting the ledger version from the transaction validation itself.
 
 ```ts filename="fetch-data.ts"
 // Wait for a transaction you just submitted

apps/nextra/pages/en/build/sdks/ts-sdk/quickstart.mdx

@@ -328,7 +328,7 @@ All told, you just learned how to transfer APT via a transaction by:
 
 1. Connecting to the network using the `Aptos` client.
 2. Creating an account.
-3. Looking up data from on-chain using client helper functions like [`aptos.getAccountModules`](https://aptos-labs.github.io/aptos-ts-sdk/@aptos-labs/ts-sdk-1.13.1/classes/Aptos.html#getAccountModules).
+3. Looking up data from on-chain using client helper functions like [`aptos.getAccountModules`](https://aptos-labs.github.io/aptos-ts-sdk/@aptos-labs/ts-sdk-1.35.0/classes/Aptos.html#getAccountModules).
 4. Signing and submitting a transaction to the network.
 5. Waiting for Aptos to execute the transaction.
 
@@ -337,5 +337,5 @@ To see all this in action, you can copy and run the full working code snippet fo
 <Callout type="info">
 For future development, make sure to bookmark the [reference docs](https://aptos-labs.github.io/aptos-ts-sdk/) to look up specific function signatures.
 
-Note that most helper functions are listed on the [`Aptos` client object](https://aptos-labs.github.io/aptos-ts-sdk/@aptos-labs/ts-sdk-1.13.1/classes/Aptos.html).
+Note that most helper functions are listed on the [`Aptos` client object](https://aptos-labs.github.io/aptos-ts-sdk/@aptos-labs/ts-sdk-1.35.0/classes/Aptos.html).
 </Callout>