Digitisation-workflow.md

@@ -2,9 +2,9 @@
 
 ## Procedural note
 
-The workflow indicated below assumes that file fixity validation is required as part of the processing. It also assumes that a tranche is populated with asset-files on the drive drive on which the tranche was initially created, rather than scenario in which the "empty" tranche is copied to an external drive, then given to the digitisation provider who populates it, and returns the tranche on an external drive, so that the tranche can be copied back to the original drive.
+The workflow indicated below assumes that file fixity validation is required as part of the processing. It also assumes that a tranche is populated with asset-files on the drive on which the tranche was initially created, rather than a scenario in which the "empty" tranche is copied to an external drive, then given to the digitisation provider who populates it, and then returns the tranche on an external drive, so that the tranche can be copied back to the original drive.
 
-If the latter is the case, each time the populated tranche is copied, the script that validates the checksums should be run, in order to ensure that no corruption has resulted from the copying. In this latter scenario, the workflow will be slightly more complex than the one indicated below.
+If the latter is the case, each time the populated tranche is copied, the script that validates the checksums should be run, in order to ensure that no corruption has occurred during the copying of the asset-files. In this latter scenario, the workflow will be slightly more complex than the one indicated below.
 
 Instructions on how to form the command line for each script can be found at the top of each script.
  
@@ -62,7 +62,7 @@ However, it is not advisable to divide up the tranches of a project according to
 
 Entering the metadata for the child-item-sets in advance of the digitisation provider becoming involved in a project has the useful by-product of allowing the identification of physical items that are missing from a collection. This allows time for replacements to be sourced in good time.
 
-Note for users of Arkivum’s Perpetua
+## Note for users of Arkivum
 
 When using Arkivum as an upload target, the gfs_create_arkivum_upload.py script has a “type of data pool” command-line-parameter. This parameter can be set to either “pres_and_acc” (preservation_and_access) or “pres” (preservation).