Update more RippleAPI mentions

content/tutorials/get-started/get-started-using-http-websocket-apis.ja.md

@@ -229,7 +229,7 @@ HTTP Status:200 OK
   - [ソフトウェアエコシステム](software-ecosystem.html)
   - [並列ネットワーク](parallel-networks.html)
 - **チュートリアル:**
-  - [RippleAPI for JavaScriptの使用開始](get-started-with-rippleapi-for-javascript.html)
+  - [xrpl.js for JavaScriptの使用開始](get-started-using-javascript.html)
   - [信頼できるトランザクションの送信](reliable-transaction-submission.html)
   - [rippledサーバーの管理](manage-the-rippled-server.html)
 - **リファレンス:**

content/tutorials/get-started/get-started-using-http-websocket-apis.md

@@ -100,15 +100,14 @@ For a full list of API methods, see:
 
 - **Concepts:**
     - [XRP Ledger Overview](xrp-ledger-overview.html)
-    - [Software Ecosystem](software-ecosystem.html)
+    - [Client Libraries](client-libraries.html)
     - [Parallel Networks](parallel-networks.html)
 - **Tutorials:**
-    - [Get Started with RippleAPI for JavaScript](get-started-with-rippleapi-for-javascript.html)
+    - [Get Started Using JavaScript](get-started-using-javascript.html)
     - [Reliable Transaction Submission](reliable-transaction-submission.html)
     - [Manage the rippled Server](manage-the-rippled-server.html)
 - **References:**
     - [rippled API Reference](rippled-api.html)
-    - [Ripple Data API v2](data-api.html)
 
 <!--{# common link defs #}-->
 {% include '_snippets/rippled-api-links.md' %}			

content/tutorials/get-started/get-started-using-javascript.md

@@ -14,7 +14,7 @@ showcase_icon: assets/img/logos/javascript.svg
 
 This tutorial guides you through the basics of building an XRP Ledger-connected application in JavaScript or TypeScript using the [`xrpl.js`](https://github.com/XRPLF/xrpl.js/) client library in either Node.js or web browsers.
 
-The scripts and config files used in this guide are [available in this website's GitHub Repository](https://github.com/XRPLF/xrpl-dev-portal/tree/master/content/_code-samples/rippleapi_quickstart).
+The scripts and config files used in this guide are [available in this website's GitHub Repository]({{github_forkurl}}/tree/{{github_branch}}/content/_code-samples/get-started/js/).
 
 
 ## Learning goals

content/tutorials/get-started/get-started.md

@@ -94,8 +94,8 @@ main()
 Try editing the code above to do something different:
 
 - Connect to the [Testnet](parallel-networks.html) public server at `wss://s.altnet.rippletest.net/` instead. [Answer >](javascript:js_interactives.step2.ex_1())
-- Look up the details of a transaction using the [`getTransaction()` method](rippleapi-reference.html#gettransaction). For the `id`, use one of the `transactionHashes` from the `getLedger()` response! [Answer >](javascript:js_interactives.step2.ex_2())
-- Convert the `totalDrops` from the response to decimal XRP. [Answer >](javascript:js_interactives.step2.ex_3())
+- Look up the details of one of the ledger's transaction using the [tx method][]. [Answer >](javascript:js_interactives.step2.ex_2())
+- Convert the `total_coins` from the response to decimal XRP. [Answer >](javascript:js_interactives.step2.ex_3())
 
 
 ## Setup Steps
@@ -111,8 +111,8 @@ This page has the necessary prerequisites already loaded, but you can access the
 
 When you're ready to move on, continue using the XRP Ledger with these resources:
 
+- [Send XRP](send-xrp.html) to send your first transaction.
 - [Understand the Concepts](concepts.html) behind the XRP Ledger's design.
-- [Use the RippleAPI Reference](rippleapi-reference.html) to see what else you can do.
 - [Install `rippled`](install-rippled.html) to participate in the network.
 - [Get Testnet XRP](xrp-testnet-faucet.html) to try sending and receiving payments.
 

content/tutorials/get-started/monitor-incoming-payments-with-websocket.md

@@ -13,7 +13,7 @@ This tutorial shows how to monitor for incoming [payments](payment-types.html) u
 
 WebSocket follows a model where the client and server establish one connection, then send messages both ways through the same connection, which remains open until explicitly closed (or until the connection fails). This is in contrast to the HTTP-based API model (including JSON-RPC and RESTful APIs), where the client opens and closes a new connection for each request.[¹](#footnote-1)<a id="from-footnote-1"></a>
 
-**Tip:** The examples in this page use JavaScript so that the examples can run natively in a web browser. If you are developing in JavaScript, you can also use the [RippleAPI library for JavaScript](rippleapi-reference.html) to simplify some tasks. This tutorial shows how to monitor for transactions _without_ using RippleAPI so that you can translate the steps to other programming languages that don't have RippleAPI.
+**Tip:** The examples in this page use JavaScript so that the examples can run natively in a web browser. If you are developing in JavaScript, you can also use the [xrpl.js library for JavaScript](https://js.xrpl.org/) to simplify some tasks. This tutorial shows how to monitor for transactions _without_ using a xrpl.js so that you can translate the steps to other programming languages that don't have a native XRP Ledger client library.
 
 ## Prerequisites
 
@@ -125,7 +125,7 @@ Since WebSocket connections can have several messages going each way and there i
 
 - For follow-up messages from [subscriptions](subscribe.html), the `type` indicates the type of follow-up message it is, such as the notification of a new transaction, ledger, or validation; or a follow-up to an ongoing [pathfinding request](path_find.html). Your client only receives these messages if it subscribes to them.
 
-**Tip:** The [RippleAPI library for JavaScript](rippleapi-reference.html) handles this step by default. All asynchronous API requests use Promises to provide the response, and you can listen to streams using the [`.on(event, callback)` method](rippleapi-reference.html#listening-to-streams).
+**Tip:** The [xrpl.js library for JavaScript](https://js.xrpl.org/) handles this step by default. All asynchronous API requests use Promises to provide the response, and you can listen to streams using the `.on(event, callback)` method of the `Client`.
 
 The following JavaScript code defines a helper function to make API requests into convenient asynchronous [Promises](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Guide/Using_promises), and sets up an interface to map other types of messages to global handlers: