From d4d937c37b3947cab372df9eb528e05489da3451 Mon Sep 17 00:00:00 2001 From: plan-do-break-fix Date: Fri, 23 Apr 2021 22:32:54 -0500 Subject: [PATCH] Correct typos in documentation --- .github/ISSUE_TEMPLATE/bug_report.md | 2 +- Builds/linux/README.md | 4 ++-- Builds/macos/README.md | 2 +- src/ripple/app/misc/FeeEscalation.md | 2 +- 4 files changed, 5 insertions(+), 5 deletions(-) diff --git a/.github/ISSUE_TEMPLATE/bug_report.md b/.github/ISSUE_TEMPLATE/bug_report.md index 57af5f3a3..e2df99600 100644 --- a/.github/ISSUE_TEMPLATE/bug_report.md +++ b/.github/ISSUE_TEMPLATE/bug_report.md @@ -22,7 +22,7 @@ assignees: '' ## Environment - + ## Supporting Files diff --git a/Builds/linux/README.md b/Builds/linux/README.md index 8fc45f435..7a82c15be 100644 --- a/Builds/linux/README.md +++ b/Builds/linux/README.md @@ -144,7 +144,7 @@ testing and running. * `-Dsan=thread` to enable the thread sanitizer with clang * `-Dsan=address` to enable the address sanitizer with clang * `-Dstatic=ON` to enable static linking library dependencies -* `-Dreporting=ON` to build code neccessary for reporting mode (defaults to OFF) +* `-Dreporting=ON` to build code necessary for reporting mode (defaults to OFF) Several other infrequently used options are available - run `ccmake` or `cmake-gui` for a list of all options. @@ -161,7 +161,7 @@ the `-j` parameter in this example tells the build tool to compile several files in parallel. This value should be chosen roughly based on the number of cores you have available and/or want to use for building. -When the build completes succesfully, you will have a `rippled` executable in +When the build completes successfully, you will have a `rippled` executable in the current directory, which can be used to connect to the network (when properly configured) or to run unit tests. diff --git a/Builds/macos/README.md b/Builds/macos/README.md index 5bc0b7c2c..b1fb86b8a 100644 --- a/Builds/macos/README.md +++ b/Builds/macos/README.md @@ -164,7 +164,7 @@ the `-j` parameter in this example tells the build tool to compile several files in parallel. This value should be chosen roughly based on the number of cores you have available and/or want to use for building. -When the build completes succesfully, you will have a `rippled` executable in +When the build completes successfully, you will have a `rippled` executable in the current directory, which can be used to connect to the network (when properly configured) or to run unit tests. diff --git a/src/ripple/app/misc/FeeEscalation.md b/src/ripple/app/misc/FeeEscalation.md index 034d59a41..c200ae075 100644 --- a/src/ripple/app/misc/FeeEscalation.md +++ b/src/ripple/app/misc/FeeEscalation.md @@ -259,7 +259,7 @@ change without warning.** [fee escalation](#fee-escalation) and [transaction queue](#transaction-queue) state as both fee levels and drops. The drop values assume a single-singed reference transaction. It is up to the user to compute the -neccessary fees for other types of transactions. (E.g. multiply all drop +necessary fees for other types of transactions. (E.g. multiply all drop values by 5 for a multi-signed transaction with 4 signatures.) The `fee` result is always instantanteous, and relates to the open