From 2c5c81815aca046c42c82445ab3f925b3c7a1f91 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?G=C3=BCnter=20Z=C3=B6chbauer?= Date: Sun, 22 Jan 2023 15:22:10 +0100 Subject: [PATCH] Fix typos (#7811) Some minor text fixes --- crates/nu-parser/README.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/crates/nu-parser/README.md b/crates/nu-parser/README.md index 8b9f863bb0..02f61a31a6 100644 --- a/crates/nu-parser/README.md +++ b/crates/nu-parser/README.md @@ -41,7 +41,7 @@ The real magic begins to happen when the parse moves on to the parsing stage. At ### Types/shapes -Each command has a shape assigned to each of the arguments in reads in. These shapes help define how the parser will handle the parse. +Each command has a shape assigned to each of the arguments it reads in. These shapes help define how the parser will handle the parse. For example, if the command is written as: @@ -49,7 +49,7 @@ For example, if the command is written as: where $x > 10 ``` -When the parsing happens, the parser will look up the `where` command and find its Signature. The Signature states what flags are allowed and what positional arguments are allowed (both required and optional). Each argument comes with it a Shape that defines how to parse values to get that position. +When the parsing happens, the parser will look up the `where` command and find its Signature. The Signature states what flags are allowed and what positional arguments are allowed (both required and optional). Each argument comes with a Shape that defines how to parse values to get that position. In the above example, if the Signature of `where` said that it took three String values, the result would be: