[writings](https://groups.google.com/forum/#!topic/comp.arch/2kYGFU4ppow),
and [mailing list
discussions](http://lists.libre-riscv.org/pipermail/libre-riscv-dev/2018-December/000261.html),
-a picture is beginning to emerge of a suibable microarchitecture.
+a picture is beginning to emerge of a suitable microarchitecture.
There are several things to remember about this design, the primary
being that it is not explicitly intended as a discrete GPU (although
one could be made). Instead, it is primarily for a battery-operated,
power-efficient hand-held device, where it happens to just about pass
-on, say, a low to mid-range chromebook. Power consumption *for the
-entire chip* is targetted at 2.5 watts.
+on, say, a low to mid-range Chromebook. Power consumption *for the
+entire chip* is targeted at 2.5 watts.
We learned quite quickly that, paradoxically, even a mobile embedded
3D GPU *requires* extreme an number of registers (128 floating-point
faced by general purpose CPUs, and when it becomes possible (or a
requirement) to access even down to the byte level of those 64-bit
registers as "elements" in a vector operation, it is even more
-challenging. Recall Mitch Alsup's scoreboard dependency floorplan
+challenging. Recall Mitch Alsup's scoreboard dependency floor plan
(reproduced with kind permission, here):
{mitch-ld-st-augmentation | link}