jupyter vsnctl idcs

Author: trevorcampbell

source/jupyter.Rmd

@@ -377,7 +377,7 @@ right-clicking on the file's name in the Jupyter file explorer, selecting
 **Open with**, and then selecting **Editor** (Figure \@ref(fig:open-data-w-editor-1)).
 Suppose you do not specify to open
 the data file with an editor. In that case, Jupyter will render a nice table
-for you, and you will not be able to see the column delimiters, and therefore
+for you, and you will not be able to see the column delimiters, \index{delimiter} and therefore
 you will not know which function to use, nor which arguments to use and values
 to specify for them.
 

source/version-control.Rmd

@@ -137,6 +137,7 @@ a workspace on a server (e.g., JupyterHub).
 The other copy is typically stored in a repository hosting service (e.g., GitHub), where
 we can easily share it with our collaborators.
 This copy is commonly referred to as \index{repository!remote} the **remote repository**.
+\index{repository|see{version control}}
 
 ```{r vc1-no-changes, fig.cap = 'Schematic of local and remote version control repositories.', fig.retina = 2, out.width="100%"}
 image_read("img/version-control/vc1-no-changes.png") |>
@@ -200,10 +201,10 @@ image_read("img/version-control/vc2-changes.png") |>
 ```
 
 Once you reach a point that you want Git to keep a record
-of the current version of your work, you need to commit
+of the current version of your work, you need to **commit** \index{git!commit}
 (i.e., snapshot) your changes. A prerequisite to this is telling Git which
 files should be included in that snapshot. We call this step **adding** the
-files to the **staging area**. \index{git!add, staging area}
+files to the **staging area**. \index{git!add, staging area}\index{staging area|see{git}}
 Note that the staging area is not a real physical location on your computer;
 it is instead a conceptual placeholder for these files until they are committed.
 The benefit of the Git version control system using a staging area is that you
@@ -309,7 +310,7 @@ Repositories can be set up with a variety of configurations, including a name,
 optional description,  and the inclusion (or not) of several template files.
 One of the most important configuration items to choose is the visibility to the outside world,
 either public or private. *Public* repositories \index{repository!public} can be viewed by anyone.
-*Private* repositories can be viewed by only you. Both public and private repositories
+*Private* repositories \index{repository!private} can be viewed by only you. Both public and private repositories
 are only editable by you, but you can change that by giving access to other collaborators.
 
 To get started with a *public* repository having a template `README.md` file, take the
@@ -530,9 +531,6 @@ image_read("img/version-control/generate-pat_03.png")
 
 ### Cloning a repository using Jupyter
 
-<!--Now that we have everything we need for authentication,
-the next step is -->
-
 *Cloning* a \index{git!clone} remote repository from GitHub
 to create a local repository results in a
 copy that knows where it was obtained from so that it knows where to send/receive