From 321b5654e2ed159d07208dcd6ae63e3de335464b Mon Sep 17 00:00:00 2001
From: Bill Traynor <wmat@riscv.org>
Date: Mon, 5 Dec 2022 21:10:21 -0500
Subject: Fixes for Ch. 6

Deleted the word Chapters before chapter references.
Fixed rendering of x0-x15
Fixed rendering of x16-x31
Changed backticks to single quotes
---
 src/rv32e.adoc | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

(limited to 'src/rv32e.adoc')

diff --git a/src/rv32e.adoc b/src/rv32e.adoc
index dca0858..ac6e74f 100644
--- a/src/rv32e.adoc
+++ b/src/rv32e.adoc
@@ -6,7 +6,7 @@ instruction sets, designed for microcontrollers in embedded systems.
 RV32E and RV64E are reduced versions of RV32I and RV64I, respectively:
 the only change is to reduce the number of integer registers to 16. This
 chapter only outlines the differences between RV32E/RV64E and
-RV32I/RV64I, and so should be read after Chapters<<rv32>> and
+RV32I/RV64I, and so should be read after <<rv32>> and
 <<rv64>>.
 (((RV32E, design)))
 [NOTE]
@@ -23,7 +23,7 @@ RV64I are also compatible with RV32E and RV64E, respectively.
 === RV32E and RV64E Programmers’ Model
 
 RV32E and RV64E reduce the integer register count to 16 general-purpose
-registers, (`x-0x15`), where `x0` is a dedicated zero register.
+registers, ('x0-x15'), where 'x0' is a dedicated zero register.
 
 [TIP]
 ====
@@ -37,13 +37,13 @@ corresponding core power reduction.
 (((RV32E, difference from RV32I)))
 
 RV32E and RV64E use the same instruction-set encoding as RV32I and RV64I
-respectively, except that only registers `x0-x15` are provided. All
-encodings specifying the other registers `x16-x31` are reserved.
+respectively, except that only registers 'x0-x15' are provided. All
+encodings specifying the other registers 'x16-x31' are reserved.
 
 [NOTE]
 ====
 The previous draft of this chapter made all encodings using the
-` x16-x31` registers available as custom. This version takes a more
+'x16-x31' registers available as custom. This version takes a more
 conservative approach, making these reserved so that they can be
 allocated between custom space or new standard encodings at a later
 date.
-- 
cgit v1.1

