Alter HLV/HSV/HLVX description to use effective privilege mode terminology (riscv#1890)

* Alter HLV/HSV/HLVX description to use effective privilege mode terminology

* get rid of duplicate effective priv mode defn, fix line width

Author: bcstrongx

src/hypervisor.adoc

@@ -1225,12 +1225,10 @@ include::images/wavedrom/hypv-virt-load-and-store.edn[]
 
 The hypervisor virtual-machine load and store instructions are valid
 only in M-mode or HS-mode, or in U-mode when `hstatus`.HU=1. Each
-instruction performs an explicit memory access as though V=1; i.e., with
-the address translation and protection, and the endianness, that apply
-to memory accesses in either VS-mode or VU-mode. Field SPVP of `hstatus`
-controls the privilege level of the access. The explicit memory access
-is done as though in VU-mode when SPVP=0, and as though in VS-mode when
-SPVP=1. As usual when V=1, two-stage address translation is applied, and
+instruction performs an explicit memory access with an effective privilege mode 
+of VS or VU. The effective privilege mode of the explicit memory access is VU 
+when `hstatus`.SPVP=0, and VS when `hstatus`.SPVP=1. As usual for VS-mode and 
+VU-mode, two-stage address translation is applied, and 
 the HS-level `sstatus`.SUM is ignored. HS-level `sstatus`.MXR makes
 execute-only pages readable by explicit loads for both stages of address translation
 (VS-stage and G-stage), whereas `vsstatus`.MXR affects only the first