Converted remaining blockquotes to callouts

Author: NotTheDr01ds

book/custom_completions.md

@@ -138,25 +138,25 @@ def my_commits [] {
 }
 ```
 
-> **Note**
->
-> with the following snippet
->
-> ```nu
-> def my-command [commit: string@my_commits] {
->     print $commit
-> }
-> ```
->
-> be aware that, even though the completion menu will show you something like
->
-> ```nu
-> >_ my-command <TAB>
-> 5c2464  Add .gitignore
-> f3a377  Initial commit
-> ```
->
-> only the value, i.e. "5c2464" or "f3a377", will be used in the command arguments!
+::: tip Note
+With the following snippet:
+
+```nu
+def my-command [commit: string@my_commits] {
+    print $commit
+}
+```
+
+... be aware that, even though the completion menu will show you something like
+
+```nu
+>_ my-command <TAB>
+5c2464  Add .gitignore
+f3a377  Initial commit
+```
+
+... only the value (i.e., "5c2464" or "f3a377") will be used in the command arguments!
+:::
 
 ## External Completions
 
@@ -174,12 +174,13 @@ For this, set the `external_completer` field in `config.nu` to a [closure](types
 
 You can configure the closure to run an external completer, such as [carapace](https://github.com/rsteube/carapace-bin).
 
-When the closure returns unparsable json (e.g. an empty string) it defaults to file completion.
+When the closure returns unparsable json (e.g., an empty string) it defaults to file completion.
 
 An external completer is a function that takes the current command as a string list, and outputs a list of records with `value` and `description` keys, like custom completion functions.
 
-> **Note**
-> This closure will accept the current command as a list. For example, typing `my-command --arg1 <tab>` will receive `[my-command --arg1 " "]`.
+::: tip Note
+This closure will accept the current command as a list. For example, typing `my-command --arg1 <tab>` will receive `[my-command --arg1 " "]`.
+:::
 
 This example will enable carapace external completions:
 

book/pipelines.md

@@ -371,16 +371,16 @@ And the pipeline:
 
 Are one and the same.
 
-> **Note**
-> the sentence _are one and the same_ above only applies for the graphical output in the shell,
-> it does not mean the two data structures are them same
->
-> ```nushell
-> > (ls) == (ls | table)
-> false
-> ```
->
-> `ls | table` is not even structured data!
+::: tip Note
+The phrase _"are one and the same"_ above only applies to the graphical output in the shell, it does not mean the two data structures are the same:
+
+```nushell
+(ls) == (ls | table)
+# => false
+```
+
+`ls | table` is not even structured data!
+:::
 
 ## Output Result to External Commands
 

book/variables.md

@@ -59,13 +59,11 @@ There are a couple of assignment operators used with mutable variables
 | `/=`     | Divides the variable by a value and makes the quotient its new value       |
 | `++=`    | Appends a list or a value to a variable                                    |
 
-> **Note**
->
-> 1. `+=`, `-=`, `*=` and `/=` are only valid in the contexts where their root operations
->    are expected to work. For example, `+=` uses addition, so it can not be used for contexts
->    where addition would normally fail
-> 2. `++=` requires that either the variable **or** the argument is a
->    list.
+::: tip Note
+
+1. `+=`, `-=`, `*=` and `/=` are only valid in the contexts where their root operations are expected to work. For example, `+=` uses addition, so it can not be used for contexts where addition would normally fail
+2. `++=` requires that either the variable **or** the argument is a list.
+   :::
 
 #### More on Mutability