diff --git a/docs/learn/101-use.md b/docs/learn/101-use.md
index 5ba05a4b..94cdcede 100644
--- a/docs/learn/101-use.md
+++ b/docs/learn/101-use.md
@@ -41,7 +41,7 @@ Dagger natively supports encrypted secrets: when a user inputs a value marked as
 (for example a password, API token or ssh key) it is automatically encrypted with that user's key,
 and no other user can access that value unless they are explicitly given access.
 
-In the interest of security, Dagger has no way *not* to encrypt a secret value.
+In the interest of security, Dagger has no way _not_ to encrypt a secret value.
 But this causes a dilemma for this tutorial: how do we give unrestricted public access to our
 (carefully sandboxed) infrastructure, so that anyone can deploy to it?
 
@@ -49,7 +49,7 @@ To solve this dilemma, we included the private key used to encrypt the tutorial'
 Simply import the key to your Dagger installation, and you're good to go:
 
 ```shell
-dagger input list || curl -sfL https://releases.dagger.io/examples/key.txt >> ~/.config/dagger/keys.txt
+./import-tutorial-key.sh
 ```
 
 ## First deployment