diff options
| author | Bill Traynor <wmat@riscv.org> | 2024-07-23 10:40:24 -0400 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2024-07-23 10:40:24 -0400 |
| commit | 65c3e057dd1bf094e1218e6d7b0014c594ae9e74 (patch) | |
| tree | 08bba4142a9afde381e1b85e296a73f4e4a7f6b4 | |
| parent | f61f5e43c697c973603922c290257b46b0e3e94b (diff) | |
| parent | 7880c719c1331eb6951baadeb20f442a7bb214c6 (diff) | |
| download | riscv-isa-manual-65c3e057dd1bf094e1218e6d7b0014c594ae9e74.zip riscv-isa-manual-65c3e057dd1bf094e1218e6d7b0014c594ae9e74.tar.gz riscv-isa-manual-65c3e057dd1bf094e1218e6d7b0014c594ae9e74.tar.bz2 | |
Merge pull request #1552 from foss-for-synopsys-dwc-arc-processors/FixTypos
Typos fix in naming.adoc and hypervisor.adoc
| -rw-r--r-- | src/hypervisor.adoc | 4 | ||||
| -rw-r--r-- | src/naming.adoc | 2 |
2 files changed, 3 insertions, 3 deletions
diff --git a/src/hypervisor.adoc b/src/hypervisor.adoc index 167a809..6137643 100644 --- a/src/hypervisor.adoc +++ b/src/hypervisor.adoc @@ -803,7 +803,7 @@ are documented in <<tinst-vals>>. .Hypervisor trap instruction (`htinst`) register. include::images/bytefield/htinstreg.edn[] -`htinst` is a *WARL* register that need only be able to hold the values that +`htinst` is a *WARL* register that only needs to be able to hold the values that the implementation may automatically write to it on a trap. [[hgatp]] @@ -1583,7 +1583,7 @@ are documented in <<tinst-vals>>. .Machine trap instruction (`mtinst`) register. include::images/bytefield/mtinstreg.edn[] -`mtinst` is a *WARL* register that need only be able to hold the values that +`mtinst` is a *WARL* register that only needs to be able to hold the values that the implementation may automatically write to it on a trap. [[two-stage-translation]] diff --git a/src/naming.adoc b/src/naming.adoc index 6ddb92a..09c728b 100644 --- a/src/naming.adoc +++ b/src/naming.adoc @@ -115,7 +115,7 @@ with the letters "Sh". If multiple hypervisor-level extensions are listed, they should be ordered alphabetically. -NOTE: Many augmentations to the hypervisor-level archtecture are more +NOTE: Many augmentations to the hypervisor-level architecture are more naturally defined as supervisor-level extensions, following the scheme described in the previous section. The "Sh" prefix is used by the few hypervisor-level extensions that have no |