docs: exposition typos

Author: ivanpanch

doc/modules/ROOT/examples/example/qrcode.cpp

@@ -26,7 +26,7 @@ int main(int argc, char** argv)
 {
     if (argc < 2) {
         std::cout << argv[0] << "\n";
-        std::cout << "Usage: qrcode <data> <width> <height> <output encoding> <error correction> <border>\n"
+        std::cout << "Usage: qrcode <data> <width> <height> <output encoding> <error correction> <margin>\n"
                      "options:\n"
                      "    <data>:             The data to encode (required)\n"
                      "    <width>:            Image width (default: 100)\n"

doc/modules/ROOT/pages/examples/magnet-link.adoc

@@ -12,7 +12,7 @@
 `magnet` is a URL scheme for identifying files by their content.
 These files are usually identified by cryptographic hash value.
 
-Magnet links are useful in peer-to-peer file sharing networks because they allow resources to be referred to without the need for a continuously available host..
+Magnet links are useful in peer-to-peer file sharing networks because they allow resources to be referred to without the need for a continuously available host.
 
 This example parses a magnet link into a new view type and prints its components to standard output.
 

doc/modules/ROOT/pages/examples/mailto.adoc

@@ -9,7 +9,7 @@
 
 = mailto URLs
 
-`mailto` is a URL scheme for email addresses. `mailto` URL are used on websites to allow users to email a specific address directly from an HTML document.
+`mailto` is a URL scheme for email addresses. `mailto` URLs are used on websites to allow users to email a specific address directly from an HTML document.
 
 This example parses a mailto URL into a new view type and prints its components to standard output.
 

doc/modules/ROOT/pages/examples/qrcode.adoc

@@ -10,7 +10,7 @@
 = QR Code
 
 A QR code is a machine-readable two-dimensional barcode.
-They might contain data for a identifier or a URL to a website.
+It might contain data for an identifier or a URL to a website.
 
 This example shows how to construct and modify URLs to consume a third party API to generate QR Codes.
 

doc/modules/ROOT/pages/examples/sanitize.adoc

@@ -25,7 +25,7 @@ communication.
 
 Using non-strict URLs directly is a security concern in
 machine-to-machine communication, is ambiguous, and also
-involve an extra cost for the transformations.
+involves an extra cost for the transformations.
 
 Different transformations are required by different applications to
 construct a valid URL appropriate for machine-to-machine communication.

doc/modules/ROOT/pages/grammar/index.adoc

@@ -19,7 +19,7 @@ to go beyond what the library offers:
 * Create new custom containers for other schemes
 * Incorporate the parsing of URLs in an enclosing grammar
 * Parse https://tools.ietf.org/html/rfc3986[rfc3986,window=blank_] elements in non-URL contexts
-  (cpp:authority_view[] is an example of this).
+  (cpp:authority_view[] is an example of this)
 * Define new ABNF rules used to parse non-URL strings
 
 To enable these use-cases, the library provides a suite of general

doc/modules/ROOT/pages/grammar/rfc3986.adoc

@@ -101,9 +101,9 @@ unreserved    = ALPHA / DIGIT / "-" / "." / "_" / "~"
 
 == URL Rules
 
-When a URL can appear in the context of a larger grammar, it may be desired to express the enclosing grammar in a single rule that incoporates the URL as an element.
+When a URL can appear in the context of a larger grammar, it may be desired to express the enclosing grammar in a single rule that incorporates the URL as an element.
 To achieve this, the library makes public the rules used to implement high-level parsing of complete strings as URL components, so that these components may be parsed as part of a larger string containing non-URL elements.
-Here we present a rule suitable for parsing the the HTTP
+Here we present a rule suitable for parsing the HTTP
 https://datatracker.ietf.org/doc/html/rfc7230#section-3.1.1[__request-line__,window=blank_]:
 
 [source,cpp]

doc/modules/ROOT/pages/grammar/rules.adoc

@@ -14,7 +14,7 @@ A __Rule__ is an object which tries to match the beginning of an input character
 It returns a cpp:boost::system::result[] containing a value if the match was successful, or an cpp:error_code[] if the match failed.
 Rules are not invoked directly.
 Instead they are passed as values to a cpp:grammar::parse[parse] function, along with the input character buffer to process.
-The first overload requires that the entire input string match, otherwise else an error occurs.
+The first overload requires that the entire input string match, otherwise an error occurs.
 The second overload advances the input buffer pointer to the first unconsumed character upon success, allowing a stream of data to be parsed sequentially:
 
 [source,cpp]
@@ -72,11 +72,11 @@ include::example$unit/doc_grammar.cpp[tag=code_grammar_1_6,indent=0]
 
 == Error Handling
 
-When a rule fails to match, or if the rule detects a unrecoverable problem with the input, it returns a result assigned from an cpp:error_code[] indicating the failure.
+When a rule fails to match, or if the rule detects an unrecoverable problem with the input, it returns a result assigned from an cpp:error_code[] indicating the failure.
 When using overloads of cpp:grammar::parse[parse] which have a character pointer as both an in and out parameter, it is up to the rule to define which character is pointed to upon error.
 When the rule matches successfully, the pointer is always changed to point to the first unconsumed character in the input, or to the cpp:end[] pointer if all input was consumed.
 
-It is the responsibilty of library and user-defined implementations of __compound rules__ (explained later) to rewind their internal pointer if a parsing operation was unsuccessful, and they wish to attempt parsing the same input using a different rule.
+It is the responsibility of library and user-defined implementations of __compound rules__ (explained later) to rewind their internal pointer if a parsing operation was unsuccessful, and they wish to attempt parsing the same input using a different rule.
 Users who extend the library's grammar by defining their own custom rules should follow the behaviors described above regarding the handling of errors and the modification of the caller's input pointer.
 
 

doc/modules/ROOT/pages/index.adoc

@@ -25,7 +25,7 @@ This library understands the grammars related to URLs and provides functionality
 == Features
 
 While the library is general purpose, special care has been taken to ensure that the implementation and data representation are friendly to network programs which need to handle URLs efficiently and securely, including the case where the inputs come from untrusted sources.
-Interfaces are provided for using error codes instead of exceptions as needed, and most algorithms have the means to opt-out of dynamic memory allocation.
+Interfaces are provided for using error codes instead of exceptions as needed, and most algorithms have the means to opt out of dynamic memory allocation.
 Another feature of the library is that all modifications leave the URL in a valid state.
 Code which uses this library is easy to read, flexible, and performant.
 

doc/modules/ROOT/pages/quicklook.adoc

@@ -234,7 +234,7 @@ id=42&name=John Doe Jingleheimer-Schmidt
 --
 ====
 
-cpp:decode_view[] and its decoding functions are designed to perform no memory allocations unless the algorithm where its being used needs the result to be in another container.
+cpp:decode_view[] and its decoding functions are designed to perform no memory allocations unless the algorithm where it's being used needs the result to be in another container.
 The design also permits recycling objects to reuse their memory, and at least minimize the number of allocations by deferring them until the result is in fact needed by the application.
 
 In the example above, the memory owned by `str` can be reused to store other results.
@@ -370,7 +370,7 @@ key = name, value = John Doe
 
 == Modifying
 
-The library provides the containers cpp:url[] and cpp:static_url[] which supporting modification of the URL contents.
+The library provides the containers cpp:url[] and cpp:static_url[] supporting modification of the URL contents.
 A cpp:url[] or cpp:static_url[] must be constructed from an existing cpp:url_view[].
 
 Unlike the cpp:url_view[], which does not gain ownership of the underlying character buffer, the cpp:url[] container uses the default allocator to control a resizable character buffer which it owns.