fix rr references

Author: oxinabox

_posts/2021-03-14-Julia-1.6-what-has-changed-since-1.0.md

@@ -133,9 +133,12 @@ The whole thing just looks more modern and polished.
 This is not useful so much for debugging Julia code, but for debugging Julia itself.
 If you get into one of the very rare situations where the language is doing something truly nonsensical, you can send a bug report recorded via `rr` and someone can debug *exactly* what is happening - even to the extent of [diagnosing faulty RAM](https://julialang.org/blog/2020/09/rr-memory-magic/).
 `rr` is an impressively cool piece of tech.
-It leverages the fact that linux's `fork` is incredibly cheap, because it takes advantage of [copy-on-write](https://en.wikipedia.org/wiki/Copy-on-write).
-`rr` basically `fork`s before every system call, and serializes what is going on; so you have a full track of everything that happened.
-The `rr` integration is really nice and easy to use; I had someone who was part of our architecture and operations team (i.e. who writes way more CloudFormation than Julia) run it to submit a support request and they had no real troubles.
+It records execution of a program, intercepting places (namely syscalls) that could be nondeterministic and storing the result.
+It can then replay the recording (even on another machine), and see exactly what happened.
+Allowing on to go into great detail on the state, and step backwards and forwards through time.
+The `rr` integration is really nice and easy to use.
+On a project I was running, I ended up getting a member of our architecture and operations team run it to submit a support request and they had no real troubles
+(And they are by no means a Julia pro, they write mostly Cloudformation).
 
 ## Syntax