From 6c12ebe7932f05cbfeb80a10a794d2255cd0aa65 Mon Sep 17 00:00:00 2001 From: Alloy Networks <45832257+alloynetworks@users.noreply.github.com> Date: Fri, 10 Dec 2021 11:50:50 +0200 Subject: [PATCH] Update ledger-history.md --- .../the-rippled-server/ledger-history/ledger-history.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/concepts/the-rippled-server/ledger-history/ledger-history.md b/content/concepts/the-rippled-server/ledger-history/ledger-history.md index 41329a6e46..868e17aa9d 100644 --- a/content/concepts/the-rippled-server/ledger-history/ledger-history.md +++ b/content/concepts/the-rippled-server/ledger-history/ledger-history.md @@ -48,7 +48,7 @@ The `[ledger_history]` setting defines a minimum number of ledgers to accumulate Some servers in the XRP Ledger network are configured as "full-history" servers. These servers, which require significantly more disk space than other tracking servers, collect all available XRP Ledger history and **do not use online deletion**. -The XRP Ledger Foundation provides access to a set of full history servers operated by community members (see https://xrplcluster.com for more details). +The XRP Ledger Foundation provides access to a set of full history servers operated by community members (see [xrplcluster.com](https://xrplcluster.com) for more details). Ripple also provides a set of public full-history servers as a public service at `s2.ripple.com`. Providers of Full History servers reserve the right to block access that is found to abuse resources, or put inordinate load on the systems.