diff --git a/article.tex b/article.tex
index fa1b7f0..f2d1344 100644
--- a/article.tex
+++ b/article.tex
@@ -17,6 +17,8 @@
 computational research, Open Science, best practices,
 genetic epidemiology
 
+% IH: replaced references to "this paper" with "this chapter". Check that ok.
+
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 \section{Introduction}
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
@@ -62,7 +64,7 @@ \section{Introduction}
 paradata can be understood in general sense as 'data about processes’ (with e.g. survey paradata
 termed alternatively as records and audit trails) \cite{nicolaas2011survey},
 or in more specific sense in relation to data collection, as 'data about the data collection process' (\cite{choumert2019using}).
-This paper uses the latter as a working definition.
+This chapter uses the latter as a working definition.
 
 % \paragraph{Code is paradata}
 
@@ -99,7 +101,9 @@ \section{Introduction}
 its benefits.
 Finally, in computational fields, 
 it can help understand how scholarly knowledge is produced (\cite{huvila2022improving}).
-This paper discusses these general reasons applied to code.
+% IH: As the series editors asked that all chapters should in the end somehow link to knowledge management, may be here could be a place to add a few words about it e.g. see below
+% IH: and to integrate this understanding as a part of the management of scholarly knowledge.
+This chapter discusses these general reasons applied to code.
 
 \begin{figure}[!htbp]
   \centering
@@ -161,7 +165,7 @@ \section{Genetic epidemiology}
 
 % \paragraph{Introduction}
 
-This paper uses genetic epidemiology as a specific example,
+This chapter uses genetic epidemiology as a specific example,
 to illustrate in which way code is paradata,
 and why this type of paradata is relevant.
 However, any field that uses computation 
@@ -180,7 +184,7 @@ \section{Genetic epidemiology}
 The trait is caused by the genetic make-up, or 'genotype'
 \iffalse
 (see Table \ref{tab:definitions} in the Supplementary Materials
-for the definitions of terms used in this paper)
+for the definitions of terms used in this chapter)
 \fi
 , of a person.
 The trait, also called 'phenotype', 
@@ -1011,7 +1015,7 @@ \section{Discussion}
 \section{Conclusions}
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 
-This paper started with some suggestions to 
+This chapter started with some suggestions to 
 make paradata useful for data re(use):
 paradata should be extensive, comprehensively documented,
 with the creation of documentation and code going hand-in-hand,
@@ -1088,12 +1092,13 @@ \section{Data Accessibility}
 \section{Author biography}
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 
-Dr. Bilderbeek has worked in computational biology for more than a decade.
-Currently, he works for the National Bioinformatics Infrastructure Sweden (NBIS)
-in Uppsala, Sweden, 
-as an application expert and trainer, with a focus on reproducible research.
-All his work can be found on GitHub at \url{https://github.com/richelbilderbeek}
-and his YouTube channel.
+% IH: Moved to a separate document
+%Dr. Bilderbeek has worked in computational biology for more than a decade.
+%Currently, he works for the National Bioinformatics Infrastructure Sweden (NBIS)
+%in Uppsala, Sweden, 
+%as an application expert and trainer, with a focus on reproducible research.
+%All his work can be found on GitHub at \url{https://github.com/richelbilderbeek}
+%and his YouTube channel.
 
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 % Bibliography
@@ -1120,13 +1125,13 @@ \section{Supplementary materials}
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
-\subsection{This paper}
+\subsection{This chapter}
 %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
 
 This book chapter has been produced following all recommendations in it:
 it's \LaTeX code is hosted on GitHub 
 at \url{https://github.com/richelbilderbeek/chapter_paradata}.
-Due this, one can, among others, see the complete version history of this paper.
+Due this, one can, among others, see the complete version history of this chapter.
 This alone could allow research to be done on, for example,
 the effect of reviewers' feedback on a first manuscript.
 The website also supplies an alternative version of the same chapter
@@ -1159,7 +1164,7 @@ \section*{Definitions}
     Trait        & A phenotype                                                                  & The concentration of IL6RA in the blood                         \\
     \hline
   \end{tabular}
-  \caption{Terms used in this paper, and their definitions}
+  \caption{Terms used in this chapter, and their definitions}
   \label{tab:definitions}
 \end{table}
 
@@ -1186,7 +1191,7 @@ \section*{Recommendations}
                   & Standardise to link between container, paper and code repository \\
     \hline
   \end{tabular}
-  \caption{Recommendations described in this paper}
+  \caption{Recommendations described in this chapter}
   \label{tab:recommendations}
 \end{table}
 
diff --git a/header.tex b/header.tex
index ed43df3..08c67f0 100644
--- a/header.tex
+++ b/header.tex
@@ -54,7 +54,7 @@
 \nonstopmode
 
 \title{
-  Making research code useful paradata
+Making research code useful paradata
 }
 \author{Richèl J.C. Bilderbeek}
 
@@ -76,7 +76,7 @@
 % \usepackage[hyphens]{url}
 
 % This is chapter number 7
-\setcounter{chapter}{6} % LaTeX adds one
+\setcounter{chapter}{1} % LaTeX adds one
 
 % This is the header of this article.
 % It contains the higher-level things, such as packages.