From 97cb638138aa714d12534ac46430af90c0caaf8f Mon Sep 17 00:00:00 2001 From: Jakub Wilk Date: Wed, 7 Dec 2016 12:49:16 +0100 Subject: [PATCH] Fix typos in documentation. --- doc/deprecated.html | 2 +- doc/design.htm | 2 +- doc/faq.htm | 2 +- doc/reference.html | 22 +++++++++++----------- doc/tickets.html | 2 +- doc/tutorial.html | 2 +- doc/v3_design.html | 2 +- 7 files changed, 17 insertions(+), 17 deletions(-) diff --git a/doc/deprecated.html b/doc/deprecated.html index 9ba05e2a..cd24d52a 100644 --- a/doc/deprecated.html +++ b/doc/deprecated.html @@ -142,7 +142,7 @@ class path - is_complere() + is_complete() ✔ is_absolute() diff --git a/doc/design.htm b/doc/design.htm index 07977cac..725131da 100644 --- a/doc/design.htm +++ b/doc/design.htm @@ -136,7 +136,7 @@ (so-called 8.3) file names.
 
  • Some operating systems allow file systems with different - characteristics to be "mounted" within a directory tree.  Thus a + characteristics to be "mounted" within a directory tree.  Thus an ISO-9660 or Windows file system may end up as a sub-tree of a POSIX directory tree.
     
    • diff --git a/doc/faq.htm b/doc/faq.htm index ec177c23..de3e08ac 100644 --- a/doc/faq.htm +++ b/doc/faq.htm @@ -54,7 +54,7 @@ not just for POSIX-based operating systems but also for Windows and the URL portion of URI's. It is ubiquitous and familiar.  On many systems, it is very easy to implement because it is -either the native operating system format (Unix and Windows) or via a +either the native operating system format (Unix and Windows) or via an operating system supplied POSIX library (z/OS, OS/390, and many more.)

    Why not use a full URI (Universal Resource Identifier) based path?

    diff --git a/doc/reference.html b/doc/reference.html index b18fee9c..bd32e0a0 100644 --- a/doc/reference.html +++ b/doc/reference.html @@ -377,7 +377,7 @@ an implied starting location. The elements of a path that determine if it is relative are operating system dependent.  [Note: Paths "." and ".." are relative paths. —end note]

    -

    canonical path [fs.def.cannonical-path]

    +

    canonical path [fs.def.canonical-path]

    An absolute path that has no elements that are symbolic links, and no "." or ".." elements.

    pathname [fs.def.pathname]

    @@ -955,7 +955,7 @@ most everyday programming.
     
  • -

    Uses where file system system errors are routine and do not necessarily represent +

    Uses where file system errors are routine and do not necessarily represent failure. Returning an error code is the most appropriate response. This allows application specific error handling, including simply ignoring the error.

    • @@ -985,7 +985,7 @@ implementation to an operating system or other underlying API results in an error that prevents the function from meeting its specifications, the system::error_code& argument is set as - appropriate appropriate for the specific error. Otherwise, clear() + appropriate for the specific error. Otherwise, clear() is called on the system::error_code& argument.
      @@ -1318,7 +1318,7 @@

    an added separator would be redundant, or

  • -

    would change an relative path to an absolute path, or

    • +

    would change a relative path to an absolute path, or

  • p.empty(), or

  • @@ -1346,7 +1346,7 @@

    an added separator would be redundant, or

  • -

    would change an relative path to an absolute path, or

    • +

    would change a relative path to an absolute path, or

  • p.empty(), or

  • @@ -1400,7 +1400,7 @@ 
    path& make_preferred();
    -

    Effects: directory-separators are converted to prefered-separators. +

    Effects: directory-separators are converted to preferred-separators. See [fs.os.examples].

    Returns: *this

    @@ -2709,7 +2709,7 @@ input iterator (C++ Std, 24.2.1, Input iterators [input.iterators]).

    A directory_iterator reads successive elements from the directory for which it was constructed, as if by calling ISO/IEC 9945 readdir_r(). After a directory_iterator is constructed, and every time operator++ is called, -it reads a directory element and stores information about it in a object of type directory_entry. operator++ is not equality preserving; that is, i == j does not imply that ++i == ++j.

    +it reads a directory element and stores information about it in an object of type directory_entry. operator++ is not equality preserving; that is, i == j does not imply that ++i == ++j.

    [Note: The practical consequence of not preserving equality is that directory iterators can only be used for single-pass algorithms. —end note]

    @@ -2761,7 +2761,7 @@ directory_iterator(const path& p, system::error_code& ec);
    -

    Effects: Constructs a iterator representing the first +

    Effects: Constructs an iterator representing the first entry in the directory p resolves to, if any; otherwise, the end iterator.

    Throws: As specified in Error reporting.

    @@ -2863,7 +2863,7 @@ recursive_directory_iterator(const path& p, system::error_code& ec);
    -

    Effects:  Constructs a iterator representing the first +

    Effects:  Constructs an iterator representing the first entry in the directory p resolves to, if any; otherwise, the end iterator.

    Postcondition: Unless the end iterator was constructed, level() == 0 && no_push_pending() == false && m_options == opt. @@ -3426,7 +3426,7 @@

    Returns: An object of type space_info. The value of the space_info object is determined as if by using ISO/IEC 9945 statvfs() to obtain a ISO/IEC 9945 struct + style="text-decoration: none">statvfs() to obtain an ISO/IEC 9945 struct statvfs, and then multiplying its f_blocks, f_bfree, and f_bavail members by its f_frsize member, @@ -4240,7 +4240,7 @@

    The create_directories, extension, basename, and replace_extension functions were developed by Vladimir Prus. The temp_directory_path function was contributed by Jeff Flinn. David Svoboda suggested the canonical function and -provided psuedo-code.

    +provided pseudo-code.

    Howard Hinnant and John Maddock reviewed a draft of the version 2 proposal, and identified a number of mistakes or weaknesses, resulting in a more polished final document.

    diff --git a/doc/tickets.html b/doc/tickets.html index 054acb40..396f9b6f 100644 --- a/doc/tickets.html +++ b/doc/tickets.html @@ -13,7 +13,7 @@

     

    Locale related

    #3332 -boost::filesystem::path will get trobule in locale Chinese_Taiwan.950 (windows)
    +boost::filesystem::path will get trouble in locale Chinese_Taiwan.950 (windows)
    #7211 path_locale destructor crashes when overloaded operator new and delete are present
    #8388 diff --git a/doc/tutorial.html b/doc/tutorial.html index e53bc2ed..51c1e372 100644 --- a/doc/tutorial.html +++ b/doc/tutorial.html @@ -611,7 +611,7 @@ results ourselves.

    • -

    The next sections show how how those changes play out, so read on!

    +

    The next sections show how those changes play out, so read on!

    Using path decomposition, plus sorting results - (tut4.cpp)

    diff --git a/doc/v3_design.html b/doc/v3_design.html index 5f1326da..1038c3c7 100644 --- a/doc/v3_design.html +++ b/doc/v3_design.html @@ -168,7 +168,7 @@ -

    When a class path function argument type matches the the operating system's +

    When a class path function argument type matches the operating system's API argument type for paths, no conversion is performed rather than conversion to a specified encoding such as one of the Unicode encodings. This avoids unintended consequences, etc.