From 68ab81b6928568f929fcf326733da08254b2f84d Mon Sep 17 00:00:00 2001 From: Amarantha Kulkarni Date: Tue, 18 Jan 2022 11:38:40 -0800 Subject: [PATCH] Update content/tutorials/manage-the-rippled-server/configuration/run-rippled-in-reporting-mode.md Co-authored-by: Rome Reginelli --- .../configuration/run-rippled-in-reporting-mode.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/tutorials/manage-the-rippled-server/configuration/run-rippled-in-reporting-mode.md b/content/tutorials/manage-the-rippled-server/configuration/run-rippled-in-reporting-mode.md index c6b7390b8b..3dcfe758b4 100644 --- a/content/tutorials/manage-the-rippled-server/configuration/run-rippled-in-reporting-mode.md +++ b/content/tutorials/manage-the-rippled-server/configuration/run-rippled-in-reporting-mode.md @@ -295,7 +295,7 @@ There are initiatives in progress to provide packages for reporting mode. The answer depends on the location of your primary datastore. If you use Cassandra as the primary datastore, the disk space requirement to run rippled in reporting mode will be lower as the data is not stored on your local disk. The PostgreSQL server can be remote as well. -Lastly, the p2p mode server only needs to keep very recent history, since reporting mode will persist long term history. +Lastly, the P2P mode server only needs to keep very recent history, while the reporting mode server keeps long term history. For more information on system requirements to run rippled, see https://xrpl.org/system-requirements.html.