Replace update rippled links

content/concepts/consensus-network/amendments.md

@@ -90,7 +90,7 @@ Becoming amendment blocked is a security feature to protect applications that de
 
 The amendments that a `rippled` server is configured to vote for or against have no impact on whether the server becomes amendment blocked. A `rippled` server always follows the set of amendments enabled by the rest of the network, to the extent possible. A server only becomes amendment blocked if an enabled amendment is not included in the amendment definitions compiled into the server's source code -- in other words, if the amendment is newer than the server.
 
-If your server is amendment blocked, you must [upgrade to a new version](update-rippled.html) to sync with the network.
+If your server is amendment blocked, you must [upgrade to a new version](install-rippled.html) to sync with the network.
 
 
 #### How to Tell If Your `rippled` Server Is Amendment Blocked
@@ -149,7 +149,7 @@ If your server is not amendment blocked, the `amendment_blocked` field is not re
 
 #### How to Unblock an Amendment-Blocked `rippled` Server
 
-Upgrade to the `rippled` version that supports the amendments that are causing your server to be amendment blocked. Ripple recommends that you [upgrade to the newest `rippled` version](update-rippled.html) to unblock your server and enable it to sync with the network again.
+Upgrade to the `rippled` version that supports the amendments that are causing your server to be amendment blocked. Ripple recommends that you [upgrade to the newest `rippled` version](install-rippled.html) to unblock your server and enable it to sync with the network again.
 
 Depending on the scenario, you may be able to (and want to) unblock your server by upgrading to a `rippled` version that is older than the newest version. This is possible if the older version supports the amendments that are blocking your `rippled` server.
 

content/news/known-amendments.md

@@ -412,7 +412,7 @@ When this amendment is activated, the XRP Ledger will undergo a brief scheduled
 
 Sorts the entries in [DirectoryNode ledger objects](directorynode.html) and fixes a bug that occasionally caused pages of owner directories not to be deleted when they should have been.
 
-**Warning:** Older versions of `rippled` that do not know about this amendment may crash when they encounter a DirectoryNode sorted by the new rules. To avoid this problem, [upgrade](update-rippled.html) to `rippled` version 0.80.0 or later.
+**Warning:** Older versions of `rippled` that do not know about this amendment may crash when they encounter a DirectoryNode sorted by the new rules. To avoid this problem, [upgrade](install-rippled.html) to `rippled` version 0.80.0 or later.
 
 
 ## SusPay

content/tutorials/manage-the-rippled-server/troubleshooting/diagnosing-problems.md

@@ -30,7 +30,7 @@ For troubleshooting purposes, the most important fields are (from most commonly
             [ips_fixed]
             s2.ripple.com 51235
 
-- **`amendment_blocked`** - This field is normally omitted from the `server_info` response. If this field appears with the value `true`, then the network has approved an [amendment](amendments.html) for which your server doesn't have an implementation. Most likely, you can fix this by [updating rippled](update-rippled.html) to the latest version. You can also use the [feature method][] to see what amendment IDs are currently enabled and which one(s) your server does and does not support.
+- **`amendment_blocked`** - This field is normally omitted from the `server_info` response. If this field appears with the value `true`, then the network has approved an [amendment](amendments.html) for which your server doesn't have an implementation. Most likely, you can fix this by [updating rippled](install-rippled.html) to the latest version. You can also use the [feature method][] to see what amendment IDs are currently enabled and which one(s) your server does and does not support.
 
 - **`peers`** - This field indicates how many other servers in the XRP Ledger peer-to-peer network your server is connected to. Healthy servers typically show between 5 and 50 peers, unless explicitly configured to connect only to certain peers.
 

content/tutorials/manage-the-rippled-server/troubleshooting/fix-sqlite-tx-db-page-size-issue.md

@@ -71,7 +71,7 @@ You can fix this issue using `rippled` on supported Linux systems according to t
 
 - You must be running **[rippled version 1.1.0][New in: rippled 1.1.0] or later**.
 
-    - [Upgrade rippled](update-rippled.html) to the latest stable version before starting this process.
+    - [Upgrade rippled](install-rippled.html) to the latest stable version before starting this process.
 
     - You can check what version of `rippled` you have installed locally by running the following command:
 

content/tutorials/manage-the-rippled-server/troubleshooting/understanding-log-messages.md

@@ -18,7 +18,7 @@ Terminating thread rippled: main: unhandled St13runtime_error
 
 If your server always crashes on startup, see [Server Won't Start](server-wont-start.html) for possible cases.
 
-If your server crashes randomly during operation or as a result of particular commands, make sure you are [updated](update-rippled.html) to the latest `rippled` version. If you are on the latest version and your server is still crashing, check the following:
+If your server crashes randomly during operation or as a result of particular commands, make sure you are [updated](install-rippled.html) to the latest `rippled` version. If you are on the latest version and your server is still crashing, check the following:
 
 - Is your server running out of memory? On some systems, `rippled` may be terminated by the Out Of Memory (OOM) Killer or another monitor process.
 - If your server is running in a shared environment, are other users or administrators causing the machine or service to be restarted? For example, some hosted providers automatically kill any service that uses a large amount of a shared machine's resources for an extended period of time.