From 9eadf6f3dd1369817eeb26fe97f92f0790aa60fa Mon Sep 17 00:00:00 2001 From: Jan Klass Date: Sat, 11 Jul 2026 23:06:40 +0200 Subject: [PATCH] Fix code fencing --- book/pipelines.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/book/pipelines.md b/book/pipelines.md index 1ac5566aad4..8383d7638f7 100644 --- a/book/pipelines.md +++ b/book/pipelines.md @@ -46,7 +46,7 @@ line1; line2 | line3 Here, semicolons are used in conjunction with pipelines. When a semicolon is used, no output data is produced to be piped. As such, the `$in` variable will not work when used immediately after the semicolon. - As there is a semicolon after `line1`, the command runs to completion and its output is discarded. -- `line2` | `line3` is a normal pipeline. It runs, and as the final value, its contents are returned and displayed. +- `line2 | line3` is a normal pipeline. It runs, and as the final value, its contents are returned and displayed. See: [Thinking in Nu -> Single Return Value per Expression](thinking_in_nu.html#single-return-value-per-expression)