Rename section "Never use eval()!" to "Never use direct eval()!" (mdn…

…#32497)

* Rename section "Never use eval()!" to "Never use direct eval()!"

- Despite the section title, the contents of the body are referring specifically to _direct_ `eval()`.

* Fix broken links after changing section name

files/en-us/web/javascript/reference/global_objects/eval/index.md

@@ -7,7 +7,7 @@ browser-compat: javascript.builtins.eval
 
 {{jsSidebar("Objects")}}
 
-> **Warning:** Executing JavaScript from a string is an enormous security risk. It is far too easy for a bad actor to run arbitrary code when you use `eval()`. See [Never use eval()!](#never_use_eval!), below.
+> **Warning:** Executing JavaScript from a string is an enormous security risk. It is far too easy for a bad actor to run arbitrary code when you use `eval()`. See [Never use direct eval()!](#never_use_direct_eval!), below.
 
 The **`eval()`** function evaluates JavaScript code represented as a string and returns its completion value. The source is parsed as a script.
 
@@ -162,7 +162,7 @@ Indirect eval can be seen as if the code is evaluated within a separate `<script
   new Ctor(); // [Function: Ctor]
   ```
 
-### Never use eval()!
+### Never use direct eval()!
 
 Using direct `eval()` suffers from multiple problems: