fix format

_episodes/03-FindingTriggerInfo.md

@@ -44,6 +44,7 @@ After retriving from the DB, you can see all the paths.
  * The L1 seed of a HLT path is always the first module (after the `HLTBeginSequence`) starting with the name `hltL1sXXXX`
  * Click on `hltL1sETM50ToETM120`
  * In the right panel, the `L1SeedsLogicalExpression` shows the L1 seeds used by the path.
+
 > ## Checklist
 > You should see the same L1 seeds that you find from OMS.
 {: .checklist}

_episodes/04-HLT_efficiency.md

@@ -26,25 +26,25 @@ We will first run this exercise on MiniAOD format, then run it again on NanoAOD.
 > The MINIAOD format was introduced at the beginning of Run 2 to reduce the information and file size from the AOD file format.<br>
 > This means that several redundant versions of Ntuples for different analysis groups are stored in the limited CMS storage spaces.<br>
 > For Run 2 analyses, most of the analysis groups at CMS skimmed the centrally produced MiniAOD files into smaller, analysis-specific ROOT Ntuples.<br>
-
-MiniAOD events contain two trigger products that we will need in these exercises.<br>
-The `TriggerResults` product contains trigger bits for each HLT path, whereas the `TriggerObjectStandAlone` product contains the trigger objects used at HLT.<br>
-In addition, the trigger prescales, L1 trigger decisions, and L1 objects are stored in MiniAOD.<br>
-A more detailed description of the trigger-related MiniAOD event content can be found [here](https://twiki.cern.ch/twiki/bin/view/CMSPublic/WorkBookMiniAOD2016#Trigger).
-
-In this exercise we work with a skimmed MiniAOD file. (In case you are wondering where this skimmed file came from: it has been created using the configuration in `ShortExerciseTrigger/test/skim_pfmet100.py`, which selects events with offline MET above a threshold of 100 GeV.)
-
-> ### Inspect MiniAOD content
-> First, inspect the contents of the skimmed MiniAOD input file as follows:
-> ~~~
-> edmDumpEventContent root://cmseos.fnal.gov//store/user/cmsdas/2023/short_exercises/Trigger/skim_pfmet100_SingleElectron_2016G_ReReco_87k.root --regex=Trigger
-> ~~~
-> You can also inspect the full file content by dropping the --regex parameter.
-{: .challenge}
-
-As you see, there are indeed multiple TriggerResults products here, as well as other trigger-related collections.<br>
-We will learn how to interact with these two products and how to use their packed information in our physics analyses in this and the following exercises.
-
+> 
+> MiniAOD events contain two trigger products that we will need in these exercises.<br>
+> The `TriggerResults` product contains trigger bits for each HLT path, whereas the `TriggerObjectStandAlone` product contains the trigger objects used at HLT.<br>
+> In addition, the trigger prescales, L1 trigger decisions, and L1 objects are stored in MiniAOD.<br>
+> A more detailed description of the trigger-related MiniAOD event content can be found [here](https://twiki.cern.ch/twiki/bin/view/CMSPublic/WorkBookMiniAOD2016#Trigger).
+> 
+> In this exercise we work with a skimmed MiniAOD file. (In case you are wondering where this skimmed file came from: it has been created using the configuration in `ShortExerciseTrigger/test/skim_pfmet100.py`, which selects events with offline MET above a threshold of 100 GeV.)
+> 
+> > ## Inspect MiniAOD content
+> > First, inspect the contents of the skimmed MiniAOD input file as follows:
+> > ~~~
+> > edmDumpEventContent root://cmseos.fnal.gov//store/user/cmsdas/2023/short_exercises/Trigger/skim_pfmet100_SingleElectron_2016G_ReReco_87k.root --regex=Trigger
+> > ~~~
+> > You can also inspect the full file content by dropping the --regex parameter.
+> {: .challenge}
+> 
+> As you see, there are indeed multiple TriggerResults products here, as well as other trigger-related collections.<br>
+> We will learn how to interact with these two products and how to use their packed information in our physics analyses in this and the following exercises.
+> 
 {: .solution}
 
 > ## NanoAOD