Skip to content

Commit 572fe02

Browse files
committed
fix typos
1 parent 40f9f19 commit 572fe02

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

blog/2025-07-22-nushell_0_106_0.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -65,7 +65,7 @@ As of [#15878], unquote file/directory paths as command arguments will no longer
6565

6666
Paths with path components such as `..` and `~` are still expanded, but paths will not automatically be expanded into their absolute form.
6767

68-
Here's an example with a simple custom command with a `path` parameter. Let's say we are in the directoy `/home/user`, and we call it with the argument `test/../bar`:
68+
Here's an example with a simple custom command with a `path` parameter. Let's say we are in the directory `/home/user`, and we call it with the argument `test/../bar`:
6969

7070
```nushell
7171
def foo [my_path: path] { $my_path }
@@ -139,7 +139,7 @@ If you want to opt in and try them out yourself, you can enable them in the foll
139139
NU_EXPERIMENTAL_OPTIONS="reorder-cell-paths,.." nu
140140
```
141141
This environment variable is **not** respected when running scripts to avoid breaking independent executable scripts.
142-
- By starting `nu` with the `--experimental-options` flag, passing in a list of option nam
142+
- By starting `nu` with the `--experimental-options` flag, passing in a list of option names.
143143
```nushell
144144
nu --experimental-options=[reorder-cell-paths,..]
145145
```
@@ -228,7 +228,7 @@ $val.foo.0
228228

229229
### Improved documentation, errors, and warnings
230230

231-
- With [#15892], text written in backticks inside help text will now be highlighted as code. If it's valid Nushell code, it will be highlighted as such. Otherwise, it will use a "dimmed" style. You can make use of this youself in custom command documentation as well! Here's what this looks like with some examples on the `select` command documentation (notice `name` and `first 4` being highlighted):
231+
- With [#15892], text written in backticks inside help text will now be highlighted as code. If it's valid Nushell code, it will be highlighted as such. Otherwise, it will use a "dimmed" style. You can make use of this yourself in custom command documentation as well! Here's what this looks like with some examples on the `select` command documentation (notice `name` and `first 4` being highlighted):
232232
![The select help documentation, with specific examples highlighted as nushell code](https://private-user-images.githubusercontent.com/8751613/456136807-a0efa0d7-fc11-4702-973b-a0b448c383e0.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NTMyODc1NjUsIm5iZiI6MTc1MzI4NzI2NSwicGF0aCI6Ii84NzUxNjEzLzQ1NjEzNjgwNy1hMGVmYTBkNy1mYzExLTQ3MDItOTczYi1hMGI0NDhjMzgzZTAucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI1MDcyMyUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNTA3MjNUMTYxNDI1WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9MGRkYzhlMDRiOTU1MGZhNDE5YTkwODc4MjViMjhhYWIxNjAzYzM3ZTRlZWZjZTVhY2RlZWUxZjgzY2U5ZmFmNiZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.J8N0gfL2c0E0knVet1tG5vcQwBIhQqQCjIvipB-Vjq4)
233233

234234
- Warnings should now be a bit more distinct: they will now show up with a orange caution symbol, rather than the same red X used for errors ([#16146])
@@ -550,7 +550,7 @@ Thanks to all the contributors below for helping us solve issues, improve docume
550550
| [@blindFS] | perf: better scalability of get_columns | [#15780] |
551551
| [@Tyarel8] | feat(std/help): Add `--help` for external-commands | [#15962] |
552552
| [@weirdan] | Support namespaces in `query xml` | [#16008] |
553-
| [@fdncred] | repect color_config.header color for record key | [#16006] |
553+
| [@fdncred] | respect color_config.header color for record key | [#16006] |
554554
| [@cptpiepmatz] | Fix: missing `installed_plugins` in `version` | [#16004] |
555555
| [@JohnSwiftC] | Add backtrack named flag to parse (issue #15997) | [#16000] |
556556
| [@cptpiepmatz] | Bump `calamine` to 0.28 | [#16003] |
@@ -589,7 +589,7 @@ Thanks to all the contributors below for helping us solve issues, improve docume
589589
| [@app/dependabot] | build(deps): bump which from 7.0.0 to 7.0.3 | [#15937] |
590590
| [@app/dependabot] | build(deps): bump titlecase from 3.5.0 to 3.6.0 | [#15936] |
591591
| [@app/dependabot] | build(deps): bump ansi-str from 0.8.0 to 0.9.0 | [#15935] |
592-
| [@liquid-dragons] | Fix docs typo referring to non-existant `Value::CustomValue` | [#15954] |
592+
| [@liquid-dragons] | Fix docs typo referring to non-existent `Value::CustomValue` | [#15954] |
593593
| [@liquid-dragons] | Improve precision in parsing of filesize values | [#15950] |
594594
| [@fdncred] | bump to dev version 0.105.2 | [#15952] |
595595
| [@hustcer] | Use NUSHELL_PAT for winget publish | [#15934] |

0 commit comments

Comments
 (0)