Update README.md

README.md

@@ -56,7 +56,7 @@ With our now deobfuscated version of the script, we can begin to determine how t
 2. `./bean` - This module seems to be in charge of all event recording (mouse, keyboard, touch).
 3. `./es5_code/obf` - This module starts the collection of device data.
 4. `./hash` - This module contains a function used to hash different values during runtime.
-5. `./helpers` - This moudle just contains a function used for safe base64 encoding.
+5. `./helpers` - This module just contains a function used for safe base64 encoding.
 6. `initial` - This is the first module to run, definition of the signals class, a checksum of different functions within the script.
 7. `./picasso` - This module is in charge of canvas fingerprinting.
 8. `./slidercaptcha` - This module loads all of the images used during the captcha into the DOM - the background image and the puzzle fragment.
@@ -87,4 +87,4 @@ Events are a bit different from the other values we will use, as we cannot hard
 Canvas fingerprinting is a technique used by numerous antibot companies, and it involves shapes being drawn in the html canvas. Each browser will render the canvas in a slightly different way than other browsers, so they most likely use it as a benchmark against the other signals being submitted. I found that we can hardcode these as long as the other signals match up with the device the canvas fingerprint was collected from
 
 #### Timestamps
-Timestamps are used frequently during the script, as Datadome will try and fingerprint these sessions by comparing our fake timestamps with those that are real. I have found it sufficient to randomly generate these timestamps within ranges of those found in real browsers.
+Timestamps are used frequently during the script, as Datadome will try and fingerprint these sessions by comparing our fake timestamps with those that are real. I have found it sufficient to randomly generate these timestamps within ranges of those found in real browsers.