From 9bec6c40df1de1bb5e62439f4b49cd2e6b771840 Mon Sep 17 00:00:00 2001
From: Gordon McCann <43148247+gwm17@users.noreply.github.com>
Date: Fri, 29 Apr 2022 16:39:29 -0400
Subject: [PATCH] Updated Details (markdown)

---
 Details.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Details.md b/Details.md
index 794f320..15c98f9 100644
--- a/Details.md
+++ b/Details.md
@@ -9,7 +9,7 @@ Most important for the performance of the code is the size of the data buffer. I
 ## `CompassRun`
 `CompassRun` is the main location of event building in the program. It serves as a hub for the separate event building operations and the collection of `CompassFiles` for the active run. `CompassRun` is given a list of filenames and loops over that list, generating either a `CompassFile` or passing the name along to the scaler analysis if it matches a name in the scaler list. Once the set of files has been created, `CompassRun` begins the event building operation of choice (fast, slow, etc.) by selecting the first hit in time from the collection of files. Once it identifies the earliest hit, it passes the hit along to the next stage, typically slow sorting. The `CompassFile` from which the hit was taken has it's flag flipped so that the next hit in the buffer is set to the active hit. This process continues until all files have been exhausted of data.
 
-## `GWMEventBuilder`
+## `EVBApp`
 This is the main API of the program. Think of this class as the application level class. It is the direct interface with the user input data, and properly generates and runs various `CompassRun` operations. If you want to add some new form of user input, it should be done through this class.
 
 ## `SlowSort, FastSort, SFPAnalyzer`