docs: fixup some things in the new tracing docs

docs/_dapp/tracing-filtered.md

@@ -6,7 +6,7 @@ sort_key: B
 In the previous section you learned how to create a complete trace. However, those traces can include the complete status of the EVM at every point
 in the execution, which is huge. Usually you are only interested in a small subset of this information. To get it, you can specify a JavaScript filter.
 
-**Note:** The JavaScript package used by Geth is [Goja](https://github.com/dop251/goja), which is only up to the
+**Note:** The JavaScript interpreter used by Geth is [duktape](https://duktape.org), which is only up to the
 [ECMAScript 5.1 standard](https://262.ecma-international.org/5.1/). This means we cannot use [arrow functions](https://www.w3schools.com/js/js_arrow_function.asp)
 and [template literals](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Template_literals).
 
@@ -341,5 +341,3 @@ or how to use the `db` parameter to know the state of the chain at the time of e
 covered [in the reference](https://geth.ethereum.org/docs/rpc/ns-debug#javascript-based-tracing).
 
 Hopefully with this tool you will find it easier to trace the EVM's behavior and debug thorny contract issues.
-
-Original version by [Ori Pomerantz](qbzzt1@gmail.com)