From 5a2fc1cb65b6bc17b653e05b8059c656f707d2ad Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?S=C3=B8ren=20Mortensen?= <soren@neros.dev>
Date: Thu, 19 Oct 2023 18:44:00 +0100
Subject: [PATCH] core: fix incorrect (incorrectly updated) docs for
 LevelFilter (#2767)

These docs were updated (in response to #1669), but the "or equal to"
phrase should have been moved to the other case.

Fixes: #1993

## Motivation

When these docs were updated in response to #1669, they were updated
incompletely (a level that is equal to a filter is _enabled_, not
_disabled_) and therefore remained incorrect.

## Solution

The docs were updated, moving the "or equal to" phrase to the other
case.
---
 tracing-core/src/metadata.rs | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/tracing-core/src/metadata.rs b/tracing-core/src/metadata.rs
index 5e475c1294..7d8448b641 100644
--- a/tracing-core/src/metadata.rs
+++ b/tracing-core/src/metadata.rs
@@ -222,10 +222,9 @@ pub struct Level(LevelInner);
 
 /// A filter comparable to a verbosity [`Level`].
 ///
-/// If a [`Level`] is considered less than a `LevelFilter`, it should be
-/// considered enabled; if greater than or equal to the `LevelFilter`,
-/// that level is disabled. See [`LevelFilter::current`] for more
-/// details.
+/// If a [`Level`] is considered less than or equal to a `LevelFilter`, it
+/// should be considered enabled; if greater than the `LevelFilter`, that level
+/// is disabled. See [`LevelFilter::current`] for more details.
 ///
 /// Note that this is essentially identical to the `Level` type, but with the
 /// addition of an [`OFF`] level that completely disables all trace