DOC: Use permalinks in BIAPs

Author: ZviBaratz

doc/source/devel/biaps/biap_0004.rst

@@ -123,7 +123,7 @@ data array.
 
 At the moment, dcmstack deals with this by wrapping the image with DICOM meta
 information in `NiftiWrapper` object : see
-https://github.com/moloney/dcmstack/blob/master/src/dcmstack/dcmmeta.py#L1185 .
+https://github.com/moloney/dcmstack/blob/d157741/src/dcmstack/dcmmeta.py#L1232.
 This object accepts a Nifti image as input, that usually contains a
 `DcmMetaExtension`, and has methods `get_meta` (to get metadata from extension),
 `split` (for taking slice specific metadata into the split parts), `meta_valid`
@@ -231,5 +231,5 @@ valid in relation to the current image.
 
 
 .. _dcmstack : https://github.com/moloney/dcmstack
-.. _DcmMetaExtension : https://github.com/moloney/dcmstack/blob/master/src/dcmstack/dcmmeta.py#L92
+.. _DcmMetaExtension : https://github.com/moloney/dcmstack/blob/d157741/src/dcmstack/dcmmeta.py#L112
 .. vim: ft=rst

doc/source/devel/biaps/biap_0006.rst

@@ -194,7 +194,7 @@ In NIfTI:
 We saw above that the MGH format refers to a volume (in our sense) as a
 *frame*.  ECAT has the same usage - a frame is a 3D volume. The fmristat
 software uses frame in the same sense, e.g., `line 32 of example.m
-<https://github.com/matthew-brett/fmristat/blob/master/fmristat/example.m#L32>`_.
+<https://github.com/matthew-brett/fmristat/blob/64ad8bf/fmristat/example.m#L32>`_.
 
 Unfortunately DICOM appears to use "frame" to mean a 2D slice.  For example,
 here is the definition of a "multi-frame image"::