about summary refs log tree commit diff
path: root/src
diff options
context:
space:
mode:
authorTshepang Lekhonkhobe <tshepang@gmail.com>2018-10-13 21:20:36 +0200
committerTshepang Lekhonkhobe <tshepang@gmail.com>2018-10-13 21:20:36 +0200
commit2bb85b236a39faa1c4fa198e85a6d0c3ef2a0eba (patch)
tree1ec3c05f46fe6d6adf849ae01f838e39cb2bba48 /src
parentf51752774bbbe48d2aabe53c86e9e91ed3a73a5d (diff)
downloadrust-2bb85b236a39faa1c4fa198e85a6d0c3ef2a0eba.tar.gz
rust-2bb85b236a39faa1c4fa198e85a6d0c3ef2a0eba.zip
doc: fix sentence structure in std::fmt
Diffstat (limited to 'src')
-rw-r--r--src/liballoc/fmt.rs2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/liballoc/fmt.rs b/src/liballoc/fmt.rs
index b49ec0ae252..a2e68a223f1 100644
--- a/src/liballoc/fmt.rs
+++ b/src/liballoc/fmt.rs
@@ -152,7 +152,7 @@
 //! Additionally, the return value of this function is [`fmt::Result`] which is a
 //! type alias of [`Result`]`<(), `[`std::fmt::Error`]`>`. Formatting implementations
 //! should ensure that they propagate errors from the [`Formatter`][`Formatter`] (e.g., when
-//! calling [`write!`]) however, they should never return errors spuriously. That
+//! calling [`write!`]). However, they should never return errors spuriously. That
 //! is, a formatting implementation must and may only return an error if the
 //! passed-in [`Formatter`] returns an error. This is because, contrary to what
 //! the function signature might suggest, string formatting is an infallible