diff --git a/docs/builtin_workflows.rst b/docs/builtin_workflows.rst
index a0da2fec..6e0db92e 100644
--- a/docs/builtin_workflows.rst
+++ b/docs/builtin_workflows.rst
@@ -510,6 +510,178 @@ the model-fitting workflows and which sampling schemes work with them.
 
 \* Not recommended
 
+.. _connectivity_matrices:
+
+*********************
+Connectivity matrices
+*********************
+
+Instead of offering a bewildering number of options for constructing connectivity matrices,
+``qsirecon`` will construct as many connectivity matrices as it can given the reconstruction
+methods.
+It is **highly** recommended that you pick a weighting scheme before you run
+these pipelines and only look at those numbers.
+If you look at more than one weighting method be sure to adjust your statistics for the
+additional comparisons.
+
+To skip this step in your workflow, you can modify an existing recon pipeline by removing the
+``action: connectivity`` section from the yaml file.
+
+.. _connectivity_atlases:
+
+Atlases
+=======
+
+The following atlases are included in ``qsirecon``.
+This means you do not need to add a ``--datasets`` argument to your command line,
+and can instead select them just with ``--atlases``.
+
+If you previously were using the default atlases in a "connectivity matrix" workflow,
+you can match the previous behavior by adding
+
+``--atlases 4S156Parcels 4S256Parcels 4S456Parcels Brainnetome246Ext AICHA384Ext Gordon333Ext AAL116``
+
+If you use one of them please be sure to cite the relevant publication.
+
+ * ``Brainnetome246Ext``: :footcite:t:`fan2016human`, extended with subcortical parcels.
+ * ``AICHA384Ext``: :footcite:t:`joliot2015aicha`, extended with subcortical parcels.
+ * ``Gordon333Ext``: :footcite:t:`gordon2016generation`, extended with subcortical parcels.
+ * ``AAL116``: :footcite:t:`tzourio2002automated`
+
+The ``qsirecon`` atlas set can be downloaded directly from
+`box  <https://upenn.box.com/shared/static/8k17yt2rfeqm3emzol5sa0j9fh3dhs0i.xz>`_.
+
+The 4S atlas combines the Schaefer 2018 cortical atlas (version v0143) :footcite:p:`Schaefer_2017`
+at 10 different resolutions (100, 200, 300, 400, 500, 600, 700, 800, 900, and 1000 parcels) with
+the CIT168 subcortical atlas :footcite:p:`pauli2018high`,
+the Diedrichson cerebellar atlas :footcite:p:`king2019functional`,
+the HCP thalamic atlas :footcite:p:`najdenovska2018vivo`,
+and the amygdala and hippocampus parcels from the HCP CIFTI subcortical parcellation
+:footcite:p:`glasser2013minimal`.
+The 4S atlas is used in the same manner across three PennLINC BIDS Apps:
+QSIRecon, XCP-D, and ASLPrep, to produce synchronized outputs across modalities.
+For more information about the 4S atlas, please see https://github.com/PennLINC/AtlasPack.
+
+Atlases are written out to the ``atlases`` subfolder, following
+`BEP038 <https://docs.google.com/document/d/1RxW4cARr3-EiBEcXjLpSIVidvnUSHE7yJCUY91i5TfM/edit?usp=sharing>`_.
+
+.. code-block::
+
+   qsirecon/
+      atlases/
+         dataset_description.json
+         atlas-<label>/
+            atlas-<label>_space-<label>_res-<label>_dseg.nii.gz
+            atlas-<label>_space-<label>_res-<label>_dseg.json
+            atlas-<label>_dseg.tsv
+
+Additionally, each atlas is warped to the subject's anatomical space and written out in the
+associated reconstruction workflows dataset.
+
+.. code-block::
+
+   qsirecon/
+      derivatives/
+         qsirecon-<suffix>/
+            sub-<label>/
+               dwi/
+                  sub-<label>_space-T1w_seg-<label>_dseg.nii.gz
+                  sub-<label>_space-T1w_seg-<label>_dseg.mif.gz
+                  sub-<label>_space-T1w_seg-<label>_dseg.json
+                  sub-<label>_space-T1w_seg-<label>_dseg.tsv
+
+
+.. _custom_atlases:
+
+Using custom atlases
+--------------------
+
+It's possible to use your own atlases provided you organize the atlases into BIDS-Atlas datasets.
+Users can control which atlases are used with the ``--atlases`` and ``--datasets`` parameters.
+
+The nifti images should be registered to the
+`MNI152NLin2009cAsym <https://github.com/PennLINC/qsirecon/blob/main/qsirecon/data/mni_1mm_t1w_lps.nii.gz>`_
+included in ``qsirecon``.
+It is essential that your images are in the LPS+ orientation and have the sform zeroed-out in the header.
+**Be sure to check for alignment and orientation** in your outputs.
+
+
+Connectivity Measures
+=====================
+
+Connectivity measures are bundled together in binary ``.mat`` files,
+rather than as atlas- and measure-specific tabular files.
+
+.. warning::
+
+   We ultimately plan to organize the connectivity matrices according to the BIDS-Connectivity BEP,
+   wherein each measure from each atlas is stored in a separate file.
+
+   Therefore, this organization will change in the future.
+
+.. code-block::
+
+   qsirecon/
+      derivatives/
+         qsirecon-<suffix>/
+            sub-<label>/[ses-<label>/]
+               dwi/
+                  <source_entities>_connectivity.mat
+
+The ``.mat`` file contains a dictionary with all of the connectivity measures specified
+by the recon spec for all of the different atlases specified by the user.
+
+For example, in the case where a user has selected a single atlas (``<atlas>``) and
+the recon spec specifies a single connectivity measure (``<measure>``),
+the ``.mat`` file will contain the following keys:
+
+.. code-block::
+
+   command                                # The command that was run
+   atlas_<atlas>_region_ids               # The region ids for the atlas (1 x n_parcels array)
+   atlas_<atlas>_region_labels            # The region labels for the atlas (1 x n_parcels array)
+   atlas_<atlas>_<measure>_connectivity   # The connectivity matrix for the atlas and measure (n_parcels x n_parcels array)
+
+
+MRtrix3 Connectivity Measures
+-----------------------------
+
+MRtrix3 connectivity workflows produce 4 structural connectome outputs for each atlas.
+The 4 connectivity matrix outputs are
+
+   * *atlas_<atlas>_radius<N>.count.connectivity*: raw streamline count based matrix
+   * *atlas_<atlas>_sift.radius<N>.count.connectivity*: sift-weighted streamline count based matrix
+   * *atlas_<atlas>_radius<N>.meanlength.connectivity*: a matrix containing mean length of raw streamlines
+   * *atlas_<atlas>_sift.radius<N>.meanlength.connectivity*: a matrix containing mean length of sifted output
+
+The number ``N`` in ``radiusN`` indicates how many mm the algorithm would search up from a
+given streamline's endpoint for a cortical region. E.g., a radius of 2 indicates that
+if a streamline ended before hitting gray matter, the search for a cortical
+termination region could be up to 2mm from the endpoint.
+
+
+DSI Studio Connectivity Measures
+--------------------------------
+
+DSI Studio has two options for how to count streamlines as "connnecting" a region pair.
+``pass`` counts a connection if any part of a streamline intersects two regions.
+``end`` requires that a streamline terminates in each region in order to be connected.
+There are some practical considerations with each choice:
+``pass`` could produce a connectivity matrix with *more* counts than the number of streamlines you requested.
+``end`` will include many fewer counts than the streamlines you requested.
+Due to the arbitrary nature of streamline tractography, the ``pass`` method is probably more realistic.
+
+Once the streamlines connecting each region pair are found, they need to be used to quantify that connection somehow.
+The streamlines connecting a region pair can by default are summarized by
+
+  * *count*: the count of streamlines
+  * *ncount*: the count of streamlines normalized by their length
+  * *mean_length*: the mean length of streamlines in millimeters
+  * *gfa*: the mean Generalized Fractional Anisotropy along the streamlines
+
+A great walkthrough of connectivity analysis with DSI Studio can be found
+`here <https://dsi-studio.labsolver.org/doc/gui_t3_whole_brain.html>`_.
+
 
 **********
 References
diff --git a/docs/connectivity_matrices.rst b/docs/connectivity_matrices.rst
deleted file mode 100644
index 7a21d386..00000000
--- a/docs/connectivity_matrices.rst
+++ /dev/null
@@ -1,142 +0,0 @@
-.. include:: links.rst
-
-.. _connectivity_matrices:
-
-#####################
-Connectivity matrices
-#####################
-
-Instead of offering a bewildering number of options for constructing connectivity matrices,
-``qsirecon`` will construct as many connectivity matrices as it can given the reconstruction
-methods.
-It is **highly** recommended that you pick a weighting scheme before you run
-these pipelines and only look at those numbers.
-If you look at more than one weighting method be sure to adjust your statistics for the
-additional comparisons.
-
-To skip this step in your workflow, you can modify an existing recon pipeline by removing the
-``action: connectivity`` section from the yaml file.
-
-.. _connectivity_atlases:
-
-*******
-Atlases
-*******
-
-The following atlases are included in ``qsirecon``.
-This means you do not need to add a ``--datasets`` argument to your command line,
-and can instead select them just with ``--atlases``.
-
-If you previously were using the default atlases in a "connectivity matrix" workflow,
-you can match the previous behavior by adding
-
-``--atlases 4S156Parcels 4S256Parcels 4S456Parcels Brainnetome246Ext AICHA384Ext Gordon333Ext AAL116``
-
-If you use one of them please be sure to cite the relevant publication.
-
- * ``Brainnetome246Ext``: :footcite:t:`fan2016human`, extended with subcortical parcels.
- * ``AICHA384Ext``: :footcite:t:`joliot2015aicha`, extended with subcortical parcels.
- * ``Gordon333Ext``: :footcite:t:`gordon2016generation`, extended with subcortical parcels.
- * ``AAL116``: :footcite:t:`tzourio2002automated`
-
-The ``qsirecon`` atlas set can be downloaded directly from
-`box  <https://upenn.box.com/shared/static/8k17yt2rfeqm3emzol5sa0j9fh3dhs0i.xz>`_.
-
-The 4S atlas combines the Schaefer 2018 cortical atlas (version v0143) :footcite:p:`Schaefer_2017`
-at 10 different resolutions (100, 200, 300, 400, 500, 600, 700, 800, 900, and 1000 parcels) with
-the CIT168 subcortical atlas :footcite:p:`pauli2018high`,
-the Diedrichson cerebellar atlas :footcite:p:`king2019functional`,
-the HCP thalamic atlas :footcite:p:`najdenovska2018vivo`,
-and the amygdala and hippocampus parcels from the HCP CIFTI subcortical parcellation
-:footcite:p:`glasser2013minimal`.
-The 4S atlas is used in the same manner across three PennLINC BIDS Apps:
-QSIRecon, XCP-D, and ASLPrep, to produce synchronized outputs across modalities.
-For more information about the 4S atlas, please see https://github.com/PennLINC/AtlasPack.
-
-Atlases are written out to the ``atlases`` subfolder, following
-`BEP038 <https://docs.google.com/document/d/1RxW4cARr3-EiBEcXjLpSIVidvnUSHE7yJCUY91i5TfM/edit?usp=sharing>`_.
-
-.. code-block::
-
-   qsirecon/
-      atlases/
-         dataset_description.json
-         atlas-<label>/
-            atlas-<label>_space-<label>_res-<label>_dseg.nii.gz
-            atlas-<label>_space-<label>_res-<label>_dseg.json
-            atlas-<label>_dseg.tsv
-
-Additionally, each atlas is warped to the subject's anatomical space and written out in the
-associated reconstruction workflows dataset.
-
-.. code-block::
-
-   qsirecon/
-      derivatives/
-         qsirecon-<suffix>/
-            sub-<label>/
-               dwi/
-                  sub-<label>_space-T1w_seg-<label>_dseg.nii.gz
-                  sub-<label>_space-T1w_seg-<label>_dseg.mif.gz
-                  sub-<label>_space-T1w_seg-<label>_dseg.json
-                  sub-<label>_space-T1w_seg-<label>_dseg.tsv
-
-
-.. _custom_atlases:
-
-Using custom atlases
-^^^^^^^^^^^^^^^^^^^^
-
-It's possible to use your own atlases provided you organize the atlases into BIDS-Atlas datasets.
-Users can control which atlases are used with the ``--atlases`` and ``--datasets`` parameters.
-
-The nifti images should be registered to the
-`MNI152NLin2009cAsym <https://github.com/PennLINC/qsirecon/blob/main/qsirecon/data/mni_1mm_t1w_lps.nii.gz>`_
-included in ``qsirecon``.
-It is essential that your images are in the LPS+ orientation and have the sform zeroed-out in the header.
-**Be sure to check for alignment and orientation** in your outputs.
-
-
-*********************
-Connectivity Measures
-*********************
-
-Connectivity measures are bundled together in binary ``.mat`` files,
-rather than as atlas- and measure-specific tabular files.
-
-.. warning::
-
-   We ultimately plan to organize the connectivity matrices accoring to the BIDS-Connectivity BEP,
-   wherein each measure from each atlas is stored in a separate file.
-
-   Therefore, this organization will change in the future.
-
-.. code-block::
-
-   qsirecon/
-      derivatives/
-         qsirecon-<suffix>/
-            sub-<label>/[ses-<label>/]
-               dwi/
-                  <source_entities>_connectivity.mat
-
-The ``.mat`` file contains a dictionary with all of the connectivity measures specified
-by the recon spec for all of the different atlases specified by the user.
-
-For example, in the case where a user has selected a single atlas (``<atlas>``) and
-the recon spec specifies a single connectivity measure (``<measure>``),
-the ``.mat`` file will contain the following keys:
-
-.. code-block::
-
-   command                                # The command that was run
-   atlas_<atlas>_region_ids               # The region ids for the atlas (1 x n_parcels array)
-   atlas_<atlas>_region_labels            # The region labels for the atlas (1 x n_parcels array)
-   atlas_<atlas>_<measure>_connectivity   # The connectivity matrix for the atlas and measure (n_parcels x n_parcels array)
-
-
-**********
-References
-**********
-
-.. footbibliography::
diff --git a/docs/index.rst b/docs/index.rst
index 7c95e075..3f18136e 100644
--- a/docs/index.rst
+++ b/docs/index.rst
@@ -14,7 +14,6 @@ Contents
    builtin_workflows
    building_workflows
    outputs
-   connectivity_matrices
    comparisons
    help
    license