From dc185f6ac20b05fffe1e6c20a4eb8a3d5135affe Mon Sep 17 00:00:00 2001 From: Bryan Boreham Date: Tue, 31 May 2022 08:50:02 +0100 Subject: [PATCH] Fix wording about pattern parser (#6264) The last sentence was saying the opposite of what it meant. Also fix 'start' to match singluar 'expression'. --- docs/sources/logql/log_queries.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/sources/logql/log_queries.md b/docs/sources/logql/log_queries.md index 636068a574..bc1051a4db 100644 --- a/docs/sources/logql/log_queries.md +++ b/docs/sources/logql/log_queries.md @@ -434,7 +434,7 @@ If a capture is not matched, the pattern parser will stop. Literals can be any sequence of UTF-8 characters, including whitespace characters. -By default, a pattern expression is anchored at the start of the log line. If the expression start with literals, then the log line must also start with the same set of literals. Use `<_>` at the beginning of the expression to anchor the expression at the start. +By default, a pattern expression is anchored at the start of the log line. If the expression starts with literals, then the log line must also start with the same set of literals. Use `<_>` at the beginning of the expression if you don't want to anchor the expression at the start. Consider the log line