boost_mirror/core
1
0
Fork 0
mirror of https://github.com/boostorg/core.git synced 2025-05-10 07:13:54 +00:00
Code Issues Packages Projects Releases Wiki Activity

Fix typos in docs (#127)

Browse Source 
* Fix typos in docs

Use "Acknowledgments" everywhere for consistency.

* amend! Fix typos in docs

Fix typos in docs

Use "Acknowledgements" everywhere for consistency.
This commit is contained in:
tocic 2022-09-19 12:53:00 +03:00 committed by GitHub
parent 0ac87736f8
commit 89852794ca
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
8 changed files with 11 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
doc/allocator_access.qbk
View File

@ -293,7 +293,7 @@ returns `a`.]]]
[endsect] [endsect]
[section Acknowledgments] [section Acknowledgements]
Glen Fernandes implemented the allocator access utilities. Glen Fernandes implemented the allocator access utilities.

2
doc/demangle.qbk
View File

@ -125,7 +125,7 @@ return `nullptr` if demangling failed.
[endsect] [endsect]
[section Acknowledgments] [section Acknowledgements]
The implementation of `core::demangle` was taken from The implementation of `core::demangle` was taken from
`boost/exception/detail/type_info.hpp`, which in turn was adapted `boost/exception/detail/type_info.hpp`, which in turn was adapted

4
doc/enable_if.qbk
View File

@ -304,8 +304,8 @@ depends on the template arguments of the class. Note that
again, the second argument to `enable_if` is not needed; the again, the second argument to `enable_if` is not needed; the
default (`void`) is the correct value. default (`void`) is the correct value.
The `enable_if_has_type` template is usable this scenario but instead of The `enable_if_has_type` template is usable in this scenario but instead of
using a type traits to enable or disable a specialization, it use a using a type trait to enable or disable a specialization, it uses a
SFINAE context to check for the existence of a dependent type inside SFINAE context to check for the existence of a dependent type inside
its parameter. For example, the following structure extracts a dependent its parameter. For example, the following structure extracts a dependent
`value_type` from T if and only if `T::value_type` exists. `value_type` from T if and only if `T::value_type` exists.

2
doc/ignore_unused.qbk
View File

@ -51,7 +51,7 @@ int fun( int foo, int bar )
[endsect] [endsect]
[section Acknowledgments] [section Acknowledgements]
`boost::ignore_unused()` was contributed by Adam Wulkiewicz. `boost::ignore_unused()` was contributed by Adam Wulkiewicz.

4
doc/pointer_traits.qbk
View File

@ -124,7 +124,7 @@ also not defined (`pointer_traits` is SFINAE-friendly).
[[`static pointer pointer_traits::pointer_to(element_type& v);`] [[`static pointer pointer_traits::pointer_to(element_type& v);`]
[[variablelist [[variablelist
[[Remark] [[Remark]
[If `element_type` is a void type, or if `T::pointer_to(v)` is not well formed, [If `element_type` is a void type, or if `T::pointer_to(v)` is not well-formed,
this member is not defined.]] this member is not defined.]]
[[Returns] [[Returns]
[A pointer to `v` obtained by calling `T::pointer_to(v)`.]]]]] [A pointer to `v` obtained by calling `T::pointer_to(v)`.]]]]]
@ -165,7 +165,7 @@ also not defined (`pointer_traits` is SFINAE-friendly).
[endsect] [endsect]
[section Acknowledgments] [section Acknowledgements]
Glen Fernandes implemented `pointer_traits` and `to_address` with reviews and Glen Fernandes implemented `pointer_traits` and `to_address` with reviews and
guidance from Peter Dimov. guidance from Peter Dimov.

2
doc/ref.qbk
View File

@ -68,7 +68,7 @@ The type-expression `boost::unwrap_reference<T>::type` is
[xinclude ref_reference.xml] [xinclude ref_reference.xml]
[section Acknowledgments] [section Acknowledgements]
`ref` and `cref` were originally part of the Tuple library by `ref` and `cref` were originally part of the Tuple library by
Jaakko J\u00E4rvi. They were "promoted to `boost::` status" by Jaakko J\u00E4rvi. They were "promoted to `boost::` status" by

4
doc/scoped_enum.qbk
View File

@ -46,7 +46,7 @@ The user can portably declare such enumeration as follows:
} }
BOOST_SCOPED_ENUM_DECLARE_END(future_errc) BOOST_SCOPED_ENUM_DECLARE_END(future_errc)
These macros allows to use `future_errc` in almost all the cases as an scoped enum. These macros allow using `future_errc` in almost all the cases as a scoped enum.
future_errc ev = future_errc::no_state; future_errc ev = future_errc::no_state;
@ -179,7 +179,7 @@ such cases.
[endsect] [endsect]
[section Acknowledgments] [section Acknowledgements]
This scoped enum emulation was developed by Beman Dawes, Vicente J. Botet Escriba and Anthony Williams. This scoped enum emulation was developed by Beman Dawes, Vicente J. Botet Escriba and Anthony Williams.

2
doc/use_default.qbk
View File

@ -11,7 +11,7 @@ Distributed under the Boost Software License, Version 1.0.
[section Overview] [section Overview]
The header <boost/core/use_default.hpp> provides the type `boost::use_default` The header <boost/core/use_default.hpp> provides the type `boost::use_default`
which is used by other Boost libraries as a sentinel type in a templates to which is used by other Boost libraries as a sentinel type in templates to
indicate defaults. indicate defaults.
[endsect] [endsect]