From 86885c52884caa2b20d0253aed5336b56e9ed255 Mon Sep 17 00:00:00 2001 From: Peter Simon Date: Thu, 22 Feb 2024 19:31:51 -0800 Subject: [PATCH] =?UTF-8?q?Fix=20typos=20in=20docstrings=20for=20`in`=20an?= =?UTF-8?q?d=20`=E2=88=89`=20(#53443)?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit --- base/operators.jl | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/base/operators.jl b/base/operators.jl index 9fc8068ddf20ea..26274307ba05c1 100644 --- a/base/operators.jl +++ b/base/operators.jl @@ -1397,7 +1397,7 @@ or `k in keys(dict)`. For the collections mentioned above, the result is always a `Bool`. When broadcasting with `in.(items, collection)` or `items .∈ collection`, both -`item` and `collection` are broadcasted over, which is often not what is intended. +`items` and `collection` are broadcasted over, which is often not what is intended. For example, if both arguments are vectors (and the dimensions match), the result is a vector indicating whether each value in collection `items` is `in` the value at the corresponding position in `collection`. To get a vector indicating whether each value @@ -1451,7 +1451,7 @@ in Negation of `∈` and `∋`, i.e. checks that `item` is not in `collection`. -When broadcasting with `items .∉ collection`, both `item` and `collection` are +When broadcasting with `items .∉ collection`, both `items` and `collection` are broadcasted over, which is often not what is intended. For example, if both arguments are vectors (and the dimensions match), the result is a vector indicating whether each value in collection `items` is not in the value at the corresponding position