diff --git a/src/software/automation_pipeline_developer.md b/src/software/automation_pipeline_developer.md
index 34f181a..75b39b4 100644
--- a/src/software/automation_pipeline_developer.md
+++ b/src/software/automation_pipeline_developer.md
@@ -44,10 +44,10 @@ The class that manages workflow at the recording level is (Params Config file): This dictionary defines status definitions and corresponding functions to execute.
+ **pipeline_handler_main** in (RecordingHandler): Main function in recording workflow
-1. Executes corresponding functions based in status.
-2. Executed every 30 minutes to check for new recordings to be handled.
-3. Send notifications for processed and failed functions.
-+ **exception_handler** in (RecordingHandler): Python decorator for error handling.
+ 1. Executes corresponding functions based in status.
+ 2. Executed every 30 minutes to check for new recordings to be handled.
+ 3. Send notifications for processed and failed functions.
+ + **exception_handler** in (RecordingHandler): Python decorator for error handling.
+ **modality_preingestion** in (RecordingHandler): Main ingestion function from recording to recording_process tables. There are subcalls depending on modality of recording (ephys or imaging).
#### Imaging preingestion main steps:
@@ -55,9 +55,9 @@ The class that manages workflow at the recording level is (RecordingHandler): Ingestion to recording_process table for an imaging recording. Get all FOVs (TIFF stacks) for the recording and assign a new job for each one with corresponding parameters fetched from selection done in automation GUI.
**AcquiredTiff populate function** in (Imaging pipeline): Auxiliar script to call **populate_Imaging_AcquiredTiff** script in MATLAB.
+ **populate_Imaging_AcquiredTiff** in (populate_Imaging_AcquiredTiff): Population calls to:
-1. **u19_imaging_pipeline.AcquiredTiff**: Each recording is divided into Tiff Splits (e.g. Mesoscope recordings contain multiple tiff stacks that will be processed independently). (Code here)
-2. **u19_imaging_pipeline.SyncImagingBehavior**: Find correspondence between virtual reality frame in the behavior experiment and Calcium Imaging frame in recording.
-(Code here)
+ 1. **u19_imaging_pipeline.AcquiredTiff**: Each recording is divided into Tiff Splits (e.g. Mesoscope recordings contain multiple tiff stacks that will be processed independently). (Code here)
+ 2. **u19_imaging_pipeline.SyncImagingBehavior**: Find correspondence between virtual reality frame in the behavior experiment and Calcium Imaging frame in recording.
+ (Code here)