From 3df0e06c64bf5a2f9745525d8adc51751c2e2d30 Mon Sep 17 00:00:00 2001 From: Richard Moore Date: Thu, 3 Feb 2022 15:25:26 -0500 Subject: [PATCH] docs: fixed typos (#2522). --- docs.wrm/concepts/security/index.wrm | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs.wrm/concepts/security/index.wrm b/docs.wrm/concepts/security/index.wrm index bb4958376..3d1c2a431 100644 --- a/docs.wrm/concepts/security/index.wrm +++ b/docs.wrm/concepts/security/index.wrm @@ -26,7 +26,7 @@ importantly securely released. [Historically](https://github.com/nodejs/node/issues/4660), ``new Buffer(16)`` would re-use old memory that had been -released. This would mean that code runnint later, may have +released. This would mean that code running later, may have access to data that was discarded. As an example of the dangers, imagine if you had used a Buffer @@ -37,9 +37,9 @@ have that left-over private key, which it could then use to steal the funds from that account. There are also many debugging tools and systems designed to -assist develoeprs inspect the memory contents of JavaScript +assist developers inspect the memory contents of JavaScript programs. In these cases, any //private key// or //mnemonic// -siiting in memory may be visible to other users on the system, +siting in memory may be visible to other users on the system, or malicious scripts. _heading: Timing Attack @@ -65,7 +65,7 @@ will. By timing how long the code took to execute, they now know whether garbage collection occured and therefore whether the simple or complex path was taken. -Advancced timing attacks are very difficult to mitigate in any +Advanced timing attacks are very difficult to mitigate in any garbage-collection-based language. Most libraries where this matters will hopefully mitigated this for you as much as possible, but it is still good to be aware of.