diff --git a/packages.qmd b/packages.qmd
index 0c7f7f4..2c982b9 100644
--- a/packages.qmd
+++ b/packages.qmd
@@ -39,7 +39,7 @@ But you could just as well start directly with an empty `{fusen}` package
 template, and then start your analysis from there. Package development with
 `{fusen}` is simply writing RMarkdown code.
 
-## Benefits of 
+## Benefits of packages
 
 Let’s first go over the benefits of turning your analysis into a package once
 again, as this is crucial.
@@ -479,7 +479,8 @@ explain how I got there). For consistency with your future use of {fusen}, you c
 
 Let’s start with the first function, `get_raw_data()`. If you compare the
 [before](https://raw.githubusercontent.com/b-rodrigues/rap4all/master/rmds/save_data_fusen.Rmd)^[https://is.gd/fusen_save_data],
-and [after](https://is.gd/anRjt4)^[https://is.gd/anRjt4], the differences are
+and [after](https://raw.githubusercontent.com/b-rodrigues/rap4all/master/rmds/flat_save_data.Rmd
+QR code)^[https://is.gd/inflate_ready_save_data], the differences are
 that we have named the chunk containing the function, `function-get_raw_data`
 and added documentation in the form of `{roxygen2}` comments. Naming the chunks
 is essential: this is how `{fusen}` knows that this chunk contains a function