diff --git a/Main_8cpp_source.html b/Main_8cpp_source.html index 4f1cfd5e65..226dca57a1 100644 --- a/Main_8cpp_source.html +++ b/Main_8cpp_source.html @@ -134,7 +134,7 @@ $(function() {
56#include <sys/types.h>
57#endif
58
-
59// Do we know the plaform we're compiling on? If you're adding new platforms
+
59// Do we know the platform we're compiling on? If you're adding new platforms
60// modify this check accordingly.
61#if !BOOST_OS_LINUX && !BOOST_OS_WINDOWS && !BOOST_OS_MACOS
62#error Supported platforms are: Linux, Windows and MacOS
diff --git a/namespaceripple.html b/namespaceripple.html index 95829c9d1d..e9eb72ebbc 100644 --- a/namespaceripple.html +++ b/namespaceripple.html @@ -8731,7 +8731,7 @@ ledger.

Transaction type identifiers.

-

These are part of the binary message format. Transaction type identifieers

+

These are part of the binary message format. Transaction type identifiers

Each ledger object requires a unique type identifier, which is stored within the object itself; this makes it possible to iterate the entire ledger and determine each object's type and verify that the object you retrieved from a given hash matches the expected type.

Warning
Since these values are included in transactions, which are signed objects, and used by the code to determine the type of transaction being invoked, they are part of the protocol. Changing them should be avoided because without special handling, this will result in a hard fork.
Note
When retiring types, the specific values should not be removed but should be marked as [[deprecated]]. This is to avoid accidental reuse of identifiers.
@@ -13570,7 +13570,7 @@ template<>

The cache is optional and need not be initialized. But because conversion is expensive (it requires a SHA-256 operation) in most cases the overhead of the cache is worth the benefit.

Parameters
- +
countThe number of entries the cache should accomodate. Zero will disable the cache, releasing any memory associated with it.
countThe number of entries the cache should accommodate. Zero will disable the cache, releasing any memory associated with it.
@@ -18376,7 +18376,7 @@ template<class T >

We can optimize verifying multiple multisignatures by splitting the data building into two parts; o A large part that is shared by all of the computations. o A small part that is unique to each signer in the multisignature.

The following methods support that optimization:

  1. startMultiSigningData provides the large part which can be shared.
    2. -
  2. finishMuiltiSigningData caps the passed in serializer with each signer's unique data.
    3. +
  3. finishMultiSigningData caps the passed in serializer with each signer's unique data.

Definition at line 95 of file Sign.cpp.