about summary refs log tree commit diff
diff options
context:
space:
mode:
authorCamelid <37223377+camelid@users.noreply.github.com>2020-08-29 20:53:40 -0700
committerGitHub <noreply@github.com>2020-08-29 20:53:40 -0700
commitbd3196282ba61ba284f4e176db3537f61b11892c (patch)
tree9e75de3e82aff6b554783ee2389accec35b4a7f8
parent80dcad9e5b060ba6f9e06499c799423037ce7733 (diff)
downloadrust-bd3196282ba61ba284f4e176db3537f61b11892c.tar.gz
rust-bd3196282ba61ba284f4e176db3537f61b11892c.zip
other branch -> `else` branch
-rw-r--r--library/std/src/primitive_docs.rs2
1 files changed, 1 insertions, 1 deletions
diff --git a/library/std/src/primitive_docs.rs b/library/std/src/primitive_docs.rs
index fc5036a1893..dfc026fb84f 100644
--- a/library/std/src/primitive_docs.rs
+++ b/library/std/src/primitive_docs.rs
@@ -222,7 +222,7 @@ mod prim_bool {}
 ///
 /// The reason is that, in the first example, there are many possible types that `!` could coerce
 /// to, because the function can return one of many concrete types. However, in the second example,
-/// the other branch returns a `0` of type `u32`, which is a concrete type that `!` can be coerced
+/// the `else` branch returns a `0` of type `u32`, which is a concrete type that `!` can be coerced
 /// to. See issue [#36375] for more information on this quirk of `!`.
 ///
 /// [#36375]: https://github.com/rust-lang/rust/issues/36375