some minor improvements

Author: thomasWeise

bibliography/bibliography.bib

@@ -688,7 +688,7 @@ @book{B1894DAZDVPB
 
 @article{B1991IWNT,
  author = a_beigel_richard,
- title = {Irrationality Without Number Theory},
+ title = {Irrationality without Number Theory},
  xdata = {j_tamm},
  date = {1991-04},
  volume = {98},

notation/terms.sty

@@ -111,7 +111,8 @@ text={linter},%
 name={linter},%
 sort={linter},%
 description={%
-A linter is a tool for analyzing static program code to identify bugs, problems, vulnerabilities, and inconsistent code styles~\cite{J1978LACPC,RJYKK2022CULTDVM}.%
+A linter is a tool for analyzing static program code to identify bugs, problems, vulnerabilities, and inconsistent code styles~\cite{J1978LACPC,RJYKK2022CULTDVM}. %
+\ruff\ is an example for a linter used in the \python\ world.%
 }%
 }%
 %

text/back/scripts.tex

@@ -12,7 +12,7 @@
 Now, our book focuses on \python\ programming, so \bash\ shell scripts are not in the center of our attention.
 We here cannot explain how \bash\ scripts work or what their syntax is.
 There exist plenty of books and resources on this interesting topic, such as~\cite{NR2005LTBSUSPCB3,Z2017MB,BN2018BC} or \url{https://www.gnu.org/software/bash/}.
-If we would include the scripts in the places where we use them in this book, then this would lead to confusion or tangents in the text which would mess up the flow of chapters.
+If we would include the scripts in the places where we use them in this book, then this would lead to confusion or tangents in the text which would mess up the flow of the chapters.
 Nevertheless, the book would be incomplete if these scripts were not provided at all.
 So we put them here, at the end of the book, where they do not hurt anyone and where the interested reader may check them out.%
 
@@ -23,14 +23,16 @@
 Then, it executes it.
 \mypy\ will print its comments and messages to the standard output.
 Finally, the script shows the \mypy\ version and exit code in a brief success or failure message (with a prepended~\expandafter\textil{\#}).
+\Cref{exec:variables:variable_types_wrong_hints_1:mypy,exec:variables:variable_types_wrong_hints_2:mypy} are example outputs of this script.
 
 \Cref{lst:bash:ruff} works basically the same way, just for \ruff.
 However, it sets a lot more parameters to \ruff.
 See, \ruff\ offers many more configuration options and many more different things that it can check for, compared to \mypy.
 In it's present form, it does not check for type errors, as far as I know, though.
 Either way, it is harder to balance the strictness of the tool and there are even some rules which are sometimes mutually exclusive.
 Hence, we compose a more complex command.
-Apart from that, this script works pretty much the same as \cref{lst:bash:mypy}.%
+Apart from that, this script works pretty much the same as \cref{lst:bash:mypy}.
+\Cref{exec:lists:lists_error:ruff,exec:lists:lists_fixed:ruff} are examples for the output of this script.%
 %
 \endhsection%
 %

text/main/basics/collections/lists/lists.tex

@@ -181,7 +181,7 @@
 \gitOutput{\programmingWithPythonCodeRepo}{.}{scripts/ruff.sh 02_collections lists_error.py}{lists:lists_error:ruff}{%
 The results of linting with \ruff\ of the program given in \cref{lst:lists:lists_error}. (We used the script given in \cref{lst:bash:ruff} on \cpageref{lst:bash:ruff} to apply \ruff.)}%
 %
-Let us apply \ruff\ to the program \textil{lists_error.py} given in \cref{lst:lists:lists_error}.
+Let us apply \ruff\ to the program \textil{lists_error.py} given in \cref{lst:lists:lists_error}, which produces the output \cref{exec:lists:lists_error:ruff}.
 \ruff\ finds two errors in this file:
 First, it complains that any python file should start with multi-line string specifying the purpose of the file.
 The use of such \pglspl{docstring} makes it easier for other programmers to understand what is done by which file in projects that are composed of multiple \python\ scripts.%