diff --git a/concept-amendments.html b/concept-amendments.html
index b5adf9eaf1..b3b2090e4c 100644
--- a/concept-amendments.html
+++ b/concept-amendments.html
@@ -95,6 +95,13 @@
Understanding the NoRipple flag
+
+ Gateway Bulletins
+
+
API Tools
+
+ Gateway Bulletins
+
+
API Tools
+
+ Gateway Bulletins
+
+
API Tools
+
+ Gateway Bulletins
+
+
API Tools
+
+ Gateway Bulletins
+
+
API Tools
+
+ Gateway Bulletins
+
+
API Tools
+
+ Gateway Bulletins
+
+
API Tools
+
+ Gateway Bulletins
+
+
API Tools
+
+ Gateway Bulletins
+
+
API Tools
rippled ledger_accept --conf=/path/to/rippled.cfg
-In stand-alone mode, rippled makes no distinction between a "closed" ledger version and a "validated" ledger version. (For more information about the difference, see The Ripple Ledger Consensus Process.)
+In stand-alone mode, rippled makes no distinction between a "closed" ledger version and a "validated" ledger version. (For more information about the difference, see The Ripple Ledger Consensus Process.)
Whenever rippled closes a ledger, it reorders the transactions according to a deterministic but hard-to-game algorithm. (This is an important part of consensus, since transactions may arrive at different parts of the network in different order.) When using rippled in stand-alone mode, you should manually advance the ledger before submitting a transaction that depends on the result of a transaction from a different address. Otherwise, the two transactions might be executed in reverse order when the ledger is closed. Note: You can safely submit multiple transactions from a single address to a single ledger, because rippled sorts transactions from the same address in ascending order by Sequence number.
diff --git a/concept-transaction-cost.html b/concept-transaction-cost.html
index 846d83debf..052d0db3ca 100644
--- a/concept-transaction-cost.html
+++ b/concept-transaction-cost.html
@@ -95,6 +95,13 @@
Understanding the NoRipple flag
+
+ Gateway Bulletins
+
+
API Tools
Local Load Cost
-Each rippled server maintains a cost threshold based on its current load. If you submit a transaction with a Fee value that is lower than current load-based transaction cost of the rippled server, that server neither applies nor relays the transaction. (Note: If you submit a transaction through an admin connection, the server applies and relays the transaction as long as the transaction meets the un-scaled minimum transaction cost.) A transaction is very unlikely to survive the consensus process unless its Fee value meets the requirements of a majority of servers.
+Each rippled server maintains a cost threshold based on its current load. If you submit a transaction with a Fee value that is lower than current load-based transaction cost of the rippled server, that server neither applies nor relays the transaction. (Note: If you submit a transaction through an admin connection, the server applies and relays the transaction as long as the transaction meets the un-scaled minimum transaction cost.) A transaction is very unlikely to survive the consensus process unless its Fee value meets the requirements of a majority of servers.
Open Ledger Cost
The rippled server has a second mechanism for enforcing the transaction cost, called the open ledger cost. A transaction can only be included in the open ledger if it meets the open ledger cost requirement in XRP. Transactions that do not meet the open ledger cost may be queued for a following ledger instead.
For each new ledger version, the server picks a soft limit on the number of transactions to be included in the open ledger, based on the number of transactions in the previous ledger. The open ledger cost is equal to the minimum un-scaled transaction cost until the number of transactions in the open ledger is equal to the soft limit. After that, the open ledger cost increases exponentially for each transaction included in the open ledger. For the next ledger, the server increases the soft limit if the current ledger contained more transactions than the soft limit, and decreases the soft limit if the consensus process takes more than 5 seconds.
diff --git a/concept-transfer-fees.html b/concept-transfer-fees.html
index fae633e28f..4aad310418 100644
--- a/concept-transfer-fees.html
+++ b/concept-transfer-fees.html
@@ -95,6 +95,13 @@
Understanding the NoRipple flag
+
+ Gateway Bulletins
+
+
API Tools
+
+ Gateway Bulletins
+
+
API Tools
+
+ Gateway Bulletins
+
+
API Tools
