fixed file endings

OWASP · Sep 29, 2022 · c619408 · c619408
1 parent 0698a1a
commit c619408
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/src/main/resources/explanations/challenge26_reason.adoc b/src/main/resources/explanations/challenge26_reason.adoc
@@ -2,4 +2,4 @@
 
 The state of the chain can be verified for any point in time by executing the state updates up until a certain block.
 
-Updating the state of the chain does not remove previous changes to state.
+Updating the state of the chain does not remove previous changes to state.
diff --git a/src/main/resources/explanations/challenge27_reason.adoc b/src/main/resources/explanations/challenge27_reason.adoc
@@ -1,4 +1,4 @@
 *Why sending secrets as inputs to smart contracts is a bad idea even if they aren't stored*
 
 Inputs to all transactions to contracts, like the state of internal storage of contracts on the chain are stored forever and are easy to query.
-Inputs to transactions are even visible before those transactions are accepted. This can lead to frontrunning by a 3rd party who has access to the pool of transactions and can send a transaction (with higher gas) that benefits from the known transaction running after it.
+Inputs to transactions are even visible before those transactions are accepted. This can lead to front-running by a 3rd party who has access to the pool of transactions and can send a transaction (with higher gas) that benefits from the known transaction running after it.
Original file line number	Diff line number	Diff line change
Expand Up		@@ -2,4 +2,4 @@

		The state of the chain can be verified for any point in time by executing the state updates up until a certain block.

		Updating the state of the chain does not remove previous changes to state.
		Updating the state of the chain does not remove previous changes to state.