docs: fix spelling on 2021-08-22 postmortem (#23595)

peteyburgers · web-flow · commit 62e3b83af69a · 2021-09-20T13:33:15.000+02:00
Spelling update
diff --git a/docs/postmortems/2021-08-22-split-postmortem.md b/docs/postmortems/2021-08-22-split-postmortem.md
@@ -16,7 +16,7 @@ This is a post-mortem concerning the minority split that occurred on Ethereum ma
 
 ###  2021-08-17 RETURNDATA corruption via datacopy
 
-On 2021-08-17, Guido Vranken submitted a report to bounty@ethereum.org. This co-incided with a geth-meetup in Berlin, so the geth team could fairly quickly analyse the issue. 
+On 2021-08-17, Guido Vranken submitted a report to bounty@ethereum.org. This coincided with a geth-meetup in Berlin, so the geth team could fairly quickly analyse the issue. 
 
 He submitted a proof of concept which called the `dataCopy` precompile, where the input slice and output slice were overlapping but shifted. Doing a `copy` where the `src` and `dest` overlaps is not a problem in itself, however, the `returnData`slice was _also_ using the same memory as a backing-array.
 

-Original file line number
+Diff line change
 ###  2021-08-17 RETURNDATA corruption via datacopy
 -On 2021-08-17, Guido Vranken submitted a report to [email protected]. This co-incided with a geth-meetup in Berlin, so the geth team could fairly quickly analyse the issue.
 +On 2021-08-17, Guido Vranken submitted a report to [email protected]. This coincided with a geth-meetup in Berlin, so the geth team could fairly quickly analyse the issue.
 He submitted a proof of concept which called the `dataCopy` precompile, where the input slice and output slice were overlapping but shifted. Doing a `copy` where the `src` and `dest` overlaps is not a problem in itself, however, the `returnData`slice was _also_ using the same memory as a backing-array.