Add toc links

Author: IanManske

blog/2024-05-28-nushell_0_94_0.md

@@ -22,11 +22,11 @@ As part of this release, we also publish a set of optional plugins you can insta
 
 # Table of content
 - [*Themes of this release / New features*](#themes-of-this-release-new-features-toc)
-    - [*Fixing path and CWD handling*](#fixing-path-and-cwd-handling)
-    - [*Case-preserving environment*](#case-preserving-environment)
-    - [*Streaming all the things*](#streaming-all-the-things)
-    - [*New language feature: raw strings*](#new-language-feature-raw-strings)
-    - [*Removal of deprecated features*](#removal-of-deprecated-features)
+    - [*Fixing path and CWD handling*](#fixing-path-and-cwd-handling-toc)
+    - [*Case-preserving environment*](#case-preserving-environment-toc)
+    - [*Streaming all the things*](#streaming-all-the-things-toc)
+    - [*New language feature: raw strings*](#new-language-feature-raw-strings-toc)
+    - [*Removal of deprecated features*](#removal-of-deprecated-features-toc)
     - [*Hall of fame*](#hall-of-fame-toc)
         - [*Bug fixes*](#bug-fixes-toc)
         - [*Enhancing the documentation*](#enhancing-the-documentation-toc)
@@ -68,28 +68,27 @@ As part of this release, we also publish a set of optional plugins you can insta
     for the list of available *containers*
 -->
 
-## Fixing path and CWD handling
+## Fixing path and CWD handling [[toc](#table-of-content)]
 
 One of our contributors, [@YizhePKU](https://github.com/YizhePKU), has started an effort to refactor how Nushell internally handles the current working directory and paths in general. Namely, Nushell aggressively canonicalizes paths instead of using logical paths which can lead to unintuitive or annoying behavior ([#2175](https://github.com/nushell/nushell/issues/2175)). Thanks to their work, `$env.CWD` and the `pwd` now support logical paths. With time, we intend to make similar to changes to other commands to make them more intuitive and consistent with the rest of Nushell. Another goal with these changes is to eliminate bugs in commands, as some commands incorrectly use the Nushell process's current working directory instead of `$env.CWD`. So far, the `grid`, `path type`, and `touch --reference` commands have been fixed, and we are aiming to bring more fixes in the next release. We kindly ask for your patience as we rework this part of Nushell, and we would appreciate if you would report any issues you encounter!
 
-## Case-preserving environment
+## Case-preserving environment [[toc](#table-of-content)]
 
 ::: warning Breaking change
 See a full overview of the [breaking changes](#breaking-changes)
 :::
 
-In an effort to allow more ergonomic cross-platform scripting, we have changed the environment in
-Nushell to be case-preserving ([#12701](https://github.com/nushell/nushell/pull/12701)). That is, environment variables keep their initial casing but can be accessed in a case-insensitive manner within Nushell. This means that accessing `$env.PATH` or `$env.Path` will now work on both unix-based systems and Windows systems. To get environment variables in a case-sensitive manner, you can use `get -s`.
+In an effort to allow more ergonomic cross-platform scripting, we have changed the environment in Nushell to be case-preserving ([#12701](https://github.com/nushell/nushell/pull/12701)). That is, environment variables keep their initial casing but can be accessed in a case-insensitive manner within Nushell. This means that accessing `$env.PATH` or `$env.Path` will now work on both unix-based systems and Windows systems. To get environment variables in a case-sensitive manner, you can use `get -s`.
 ```nushell
 $env | get -s PATH
 ```
 Please note that there are still a few things that have to be ironed out with this new behavior. For example, it is currently unclear what `load-env { FOO: BAR, foo: bar }` should do. So, there may be more changes in the near future.
 
-## Streaming all the things
+## Streaming all the things [[toc](#table-of-content)]
 
 Another major effort with this release was to make streaming more consistent and widespread ([#12774](https://github.com/nushell/nushell/pull/12774), [#12897](https://github.com/nushell/nushell/pull/12897), [#12918](https://github.com/nushell/nushell/pull/12918), and more). For example, Nushell now passes operating system pipe descriptors directly to external commands, meaning there should be an improvement to throughput for some pipelines. Additionally, several commands were reworked so that they are now able to stream their output in more cases instead of having to collect it all in memory beforehand. The commands in question include `from csv`, `to csv`, `from tsv`, `to tsv`, `from json --objects`, `take`, `skip`, `first`, `last`, `bytes ends-with`, `bytes collect`, `str join`, `into string`, and `into binary`. Of course, the plan is to add more commands to this list in the future, so this is only the beginning!
 
-## New language feature: raw strings
+## New language feature: raw strings [[toc](#table-of-content)]
 
 This release adds a new type of string literal to the language: raw strings ([#9956](https://github.com/nushell/nushell/pull/9956)). These are just like single quoted strings, except that raw strings may also contain single quotes. This is possible, since raw strings are enclosed by a starting `r#'` and an ending `'#`. This syntax should look familiar to users of Rust.
 ```nushell
@@ -102,7 +101,7 @@ Additional `#` symbols can be added to the start and end of the raw string to en
 r###'this text has multiple '## symbols'###
 ```
 
-## Removal of deprecated features
+## Removal of deprecated features [[toc](#table-of-content)]
 
 ::: warning Breaking change
 See a full overview of the [breaking changes](#breaking-changes)