Tidy up one last mention of EntityMap.

cranelift/rustc.md

@@ -51,13 +51,14 @@ such a thing might look like, including:
  - Build an optimizer IR without the constraints of fast-debug-build
    compilation. Cranelift's base IR is focused on Codegen, so a
    full-strength optimizer would either use an IR layer on top of it
-   (possibly using Cranelift's flexible EntityMap system), or possibly
+   (possibly using cranelift-entity's flexible `SecondaryMap`s), or
-   an independent IR that could be translated to/from the base IR.
+   possibly an independent IR that could be translated to/from the base
-   Either way, this overall architecture would keep the optimizer out
+   IR. Either way, this overall architecture would keep the optimizer
-   of the way of the non-optimizing build path, which keeps that path
+   out of the way of the non-optimizing build path, which keeps that
-   fast and simple, and gives the optimizer more flexibility. If we
+   path fast and simple, and gives the optimizer more flexibility. If we
-   then want to base the IR on a powerful data structure like the Value
+   then want to base the IR on a powerful data structure like the
-   State Dependence Graph (VSDG), we can do so with fewer compromises.
+   Value State Dependence Graph (VSDG), we can do so with fewer
+   compromises.
 
 And, these ideas build on each other. For example, one of the challenges
 for dependence-graph-oriented IRs like the VSDG is getting good enough