Fix some broken links

content/concepts/the-rippled-server/rippled-server-modes.ja.md

@@ -60,6 +60,17 @@ XRP Ledgerの堅牢性は、バリデータが相互に接続されたネット
 
 **注意:** スタンドアロンモードでは[レジャーを手動で進める](advance-the-ledger-in-stand-alone-mode.html)必要があります。
 
+## レポーティングモード
+[導入: rippled 1.7.0][][]
+
+<!-- TODO: translate this section -->
+Reporting mode is specialized mode for serving API requests more efficiently. In this mode, the server gets the latest validated ledger data over [gRPC](https://xrpl.org/configure-grpc.html) from a separate `rippled` server running in P2P Mode, then loads that data into a relational database ([PostgreSQL](https://www.postgresql.org/)). The reporting mode server does not directly participate in the peer-to-peer network, though it can forward requests such as transaction submission to the P2P Mode server it uses.
+
+Multiple reporting mode servers can share access to a PostgreSQL database and [Apache Cassandra](https://cassandra.apache.org/) cluster to serve a large amount of history without each server needing a redundant copy of all the data. Reporting mode servers provide this data through the same [`rippled` APIs](rippled-api.html) with some slight changes to accommodate for the differences in how they store the underlying data.
+
+Most notably, reporting mode servers do not report pending, non-validated ledger data or transactions. This limitation is relevant to certain use cases that rely on rapid access to in-flux data, such as performing arbitrage in the [decentralized exchange](decentralized-exchange.html).
+
+
 
 ## 関連項目
 
@@ -70,7 +81,7 @@ XRP Ledgerの堅牢性は、バリデータが相互に接続されたネット
 - **チュートリアル:**
   - [`rippled`の構成](configure-rippled.html)
     - [バリデータとしての`rippled`の実行](run-rippled-as-a-validator.html)
-  - [スタンドアロンモードでのrippledの使用](use-stand-alone-mode.html): 
+  - [スタンドアロンモードでのrippledの使用](use-stand-alone-mode.html):
     - [スタンドアロンモードでの新しいジェネシスレジャーの開始](start-a-new-genesis-ledger-in-stand-alone-mode.html)
     - [スタンドアロンモードでの保存済みレジャーの読み込み](load-a-saved-ledger-in-stand-alone-mode.html)
     - [スタンドアロンモードでレジャーを進める](advance-the-ledger-in-stand-alone-mode.html)

content/references/rippled-api/api-conventions/error-formatting.md

@@ -114,3 +114,9 @@ All methods can potentially return any of the following values for the `error` c
 - `tooBusy` - The server is under too much load to do this command right now. Generally not returned if you are connected as an admin.
 - `unknownCmd` - The request does not contain a [command](rippled-api.html) that the `rippled` server recognizes.
 - `wsTextRequired` - (WebSocket only) The request's [opcode](https://tools.ietf.org/html/rfc6455#section-5.2) is not text. <!-- SPELLING_IGNORE: opcode -->
+
+
+<!--{# common link defs #}-->
+{% include '_snippets/rippled-api-links.md' %}			
+{% include '_snippets/tx-type-links.md' %}			
+{% include '_snippets/rippled_versions.md' %}

content/tutorials/use-simple-xrp-payments/send-xrp.md

@@ -423,7 +423,7 @@ api = new ripple.RippleAPI({server: 'wss://s1.ripple.com:51233'})
 api.connect()
 ```
 
-If you [install `rippled`](install-rippled.html) yourself, it connects to the production network by default. (You can also [configure it to connect to the test net](connect-your-rippled-to-the-xrp-test-net.html) instead.) After the server has synced (typically within about 15 minutes of starting it up), you can connect RippleAPI to it locally, which has [various benefits](rippled-server-modes.html#reasons-to-run-a-stock-server). The following example shows how to connect RippleAPI to a server running the default configuration:
+If you [install `rippled`](install-rippled.html) yourself, it connects to the production network by default. (You can also [configure it to connect to the test net](connect-your-rippled-to-the-xrp-test-net.html) instead.) After the server has synced (typically within about 15 minutes of starting it up), you can connect RippleAPI to it locally, which has [various benefits](the-rippled-server.html). The following example shows how to connect RippleAPI to a server running the default configuration:
 
 ```js
 ripple = require('ripple-lib')

dactyl-config.yml

@@ -144,10 +144,14 @@ targets:
             "basic-data-types.html#account-sequence": "basic-data-types.html#アカウントシーケンス"
             "xrp.html#xrp-properties": "xrp.html#xrpの特性"
             # Fix links from untranslated health-check.html:
-            "rippled-server-modes.htmlstand-alone-mode": "rippled-server-modes.html#rippledサーバーをスタンドアロンモードで実行する理由"
+            "rippled-server-modes.html#stand-alone-mode": "rippled-server-modes.html#rippledサーバーをスタンドアロンモードで実行する理由"
             "server-doesnt-sync.html#normal-syncing-behavior": "server-doesnt-sync.html#通常の同期動作"
             # Fix link from untranslated negativeunl.html:
             "consensus.html#validation": "consensus.html#検証"
+            # Fix link from untranslated tickets.html:
+            "consensus.html#calculate-and-share-validations": "consensus.html#検証の計算と共有"
+            # Fix link from untranslated manifest.html:
+            "rippled-server-modes.html#reporting-mode": "rippled-server-modes.html#レポーティングモード"
 
 
     -   name: xrp-api-only