From 5bde713bbc612a6ef5512647dc13dded7aaeeb11 Mon Sep 17 00:00:00 2001
From: Alejandro Garcia <agarciafdz@gmail.com>
Date: Fri, 13 Feb 2026 11:01:57 -0600
Subject: [PATCH] Making the parser error explicit

If a user typed the error as it was originally it wouldn't trigger the expected parsing error.

With this modification now the error message, appears as it is expected in the document.
---
 book/thinking_in_nu.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/book/thinking_in_nu.md b/book/thinking_in_nu.md
index 8b80ca40ba5..ca43d4fba95 100644
--- a/book/thinking_in_nu.md
+++ b/book/thinking_in_nu.md
@@ -270,8 +270,8 @@ The following examples use the [`source` command](/commands/docs/source.md), but
 Consider this scenario:
 
 ```nu
-"print Hello" | save output.nu
-source output.nu
+("print Hello" | save output.nu;
+source output.nu)
 # => Error: nu::parser::sourced_file_not_found
 # =>
 # =>   × File not found