[pre-commit.ci] auto fixes from pre-commit.com hooks

for more information, see https://pre-commit.ci

docs/roman/associations/skycell_asn.rst

@@ -26,19 +26,19 @@ for the output associations. To get a complete list of options you can run the c
 
 .. code-block:: python
 
-		skycell_asn -h 
+		skycell_asn -h
 
 
 By knowing the structure of the conventional file name you can generate custom associations based
-on the information included in the file names. 
+on the information included in the file names.
 The current naming convention for the input files consists of a Visit_ID + Exposure_ID + detector + suffix
 Where the Visit_ID is a 19 digit string
 PPPPPCCAAASSSOOOVVV, with
 
 PPPPP = Program number
 CC = Execution plan number
 AAA = Pass number (within execution plan)
-SSS = Segment Number (within pass)  
+SSS = Segment Number (within pass)
 OOO = Observation number (within the leg, not to be confused with the Observation ID)
 VVV = Visit Number (within the observation)
 
@@ -81,10 +81,10 @@ or for the selections above
 
 where the skycell name can vary based on the location on the celestial sphere and the i2d indicates
 that this is resampled 2-d imaging data. The release product name can be changed from the default
-by adding the optional argument --release-product <new name> to the command line. 
-	
+by adding the optional argument --release-product <new name> to the command line.
+
 An analogous command to generate the pass level products, again setting segment to 003 to only select
-the F158 filter. 
+the F158 filter.
 
 .. code-block:: text
 

pyproject.toml

@@ -91,7 +91,7 @@ schema_editor = "romancal.scripts.schema_editor:main"
 schemadoc = "romancal.scripts.schemadoc:main"
 verify_install_requires = "romancal.scripts.verify_install_requires:main"
 asn_from_list = "romancal.associations.asn_from_list:Main"
-skycell_asn = "romancal.associations.skycell_asn:Main" 
+skycell_asn = "romancal.associations.skycell_asn:Main"
 
 [build-system]
 requires = [