From 95b52f964884fc24357150a5b62fa2f0fedd9358 Mon Sep 17 00:00:00 2001
From: Hanno Becker <beckphan@amazon.co.uk>
Date: Sat, 23 Dec 2023 06:36:47 +0000
Subject: [PATCH] Minor changes to github pages

---
 docs/faq.md   | 7 +++----
 docs/index.md | 6 +++---
 2 files changed, 6 insertions(+), 7 deletions(-)

diff --git a/docs/faq.md b/docs/faq.md
index 07b87957..d8bc21f9 100644
--- a/docs/faq.md
+++ b/docs/faq.md
@@ -9,8 +9,8 @@ layout: default
 #### Is SLOTHY a peephole optimizer?
 
 No. SLOTHY is a _fixed-instruction_ super-optimizer: It keeps instructions and optimizes
-register allocation, instruction scheduling, and software pipelining. It is the developer's responsibility 
-to map the workload at hand to the target architecture.
+register allocation, instruction scheduling, and software pipelining. It is the developer's or another tool's
+responsibility to map the workload at hand to the target architecture.
 
 <!-- #### When should I use SLOTHY?
 
@@ -21,8 +21,7 @@ is beneficial (e.g. because other code-generation techniques do not find ideal i
 #### Is SLOTHY better than {name your favourite superoptimizer}?
 
 Most likely, they serve different purposes. SLOTHY aims to do one thing well: Optimization _after_ instruction selection.
-It is thus independent of and potentially combinable with superoptimizers operating at earlier stages of the code-generation process, 
-notably peephole optimizers such as [souper](https://github.com/google/souper) and [CryptOpt](https://github.com/0xADE1A1DE/CryptOpt).
+It is thus independent of and potentially combinable with superoptimizers operating at earlier stages of the code-generation process, such as [souper](https://github.com/google/souper) and [CryptOpt](https://github.com/0xADE1A1DE/CryptOpt).
 
 #### Does SLOTHY support x86?
 
diff --git a/docs/index.md b/docs/index.md
index b3861f95..7c3d8df5 100644
--- a/docs/index.md
+++ b/docs/index.md
@@ -12,14 +12,14 @@ super-optimizes:
 `SLOTHY` enables a development workflow where developers write 'clean' assembly by hand, emphasizing the logic of the
 computation, while `SLOTHY` automates microarchitecture-specific micro-optimizations. Since `SLOTHY` does not change
 instructions, and scheduling/allocation optimizations are tightly controlled through configurable and extensible
-constraints, the developer keeps close control over the final assembly, while being freed from the most tedious and
-readability- and verifiability-impeding micro-optimizations.
+constraints, the developer keeps close control over the final assembly, while being freed from tedious
+micro-optimizations.
 
 See also [FAQ](faq.md)
 
 #### Architecture/Microarchitecture support
 
-`SLOTHY` is generic in the target architecture and microarchitecture. So far, it supports Cortex-M55 and Cortex-M85
+`SLOTHY` is generic in the target architecture and microarchitecture. It currently supports Cortex-M55 and Cortex-M85
 implementing Armv8.1-M + Helium, and Cortex-A55 and Cortex-A72 implementing
 Armv8-A + Neon. Moreover, there is an experimental model for Cortex-X/Neoverse-V cores.