[pre-commit.ci lite] apply automatic fixes

src/main/resources/explanations/challenge35.adoc

@@ -6,7 +6,7 @@ Can you spot the mistake? Can you find the value of the generated key?
 =======
 === Git Notes
 
-Git commits can be a constant pain point. 
+Git commits can be a constant pain point.
 It is fine using a short message, unintelligible garble or mashing the keyboard in a git message until you have the unfortunate task of reviewing past commits and trying to figure out what has happened.
 Git notes is here to solve this, it has been around for a while but often gets overlooked.
 Add extra metadata about the commit without affecting the commit message itself.

src/main/resources/explanations/challenge35_hint.adoc

@@ -6,7 +6,7 @@ This challenge can be solved by replaying the Key derivation function with the g
 - Copy the used parameters to an online https://www.dcode.fr/pbkdf2-hash[generator] and execute it
 - The website will return the value of the key.
 =======
-Like other Git challenges this can be solved by manually combing the Git metadata. 
+Like other Git challenges this can be solved by manually combing the Git metadata.
 There are also a plethora of tools that will automatically search for secrets leaked in Git repos.
 
 1. Search manually using `git log`. You can then use a tool such as grep to try and find leaked secrets with regex searches.

src/main/resources/explanations/challenge35_reason.adoc

@@ -8,7 +8,7 @@ KDFs should be used to generate keys based on dynamic input, such as human-suppl
 *Why you should be careful with Git notes?*
 
 When developers use Git notes they can also expose secrets if developers inadvertently include sensitive information, such as passwords or API keys, in the notes.
-Unlike regular commits, notes are not easily visible in code reviews, so they can go unnoticed for a long time. 
+Unlike regular commits, notes are not easily visible in code reviews, so they can go unnoticed for a long time.
 
 Although manually going through Git notes to look for secrets would be cumbersome, there are many tools attackers could use to search through Git repo's to look for these leaked secrets.
 >>>>>>> cefa8809 ( Feature(#614): Added test files)