diff --git a/README.md b/README.md
index ffb3ad8ac863d842a8994f419e4ef5628f80ab15..f5c77a9489161ab7ea2ceae510bdeb16f95f65b5 100644
--- a/README.md
+++ b/README.md
@@ -2,7 +2,8 @@
 
 This repo is the top-level repository which contains an example accelerator based on the secworks AES engine integrated in SoC Labs provided nanosoc chip design IP in forms of git subrepositories.
 
-## Cloning this repository
+### Cloning this repository
+---
 
 This Repository contains multiple sub-repositories. In order to clone them with this repository, please use the following command:
 
@@ -14,7 +15,8 @@ In order to checkout all the sub-repositories in your project to their branches
 
 `source set_env.sh`
 
-## Setting up your environment
+### Setting up the Project Environment
+---
 
 Every time you wish to run commands in this project, you will need to make sure the set environment script has been run for your current terminal session. This is done by moving to the top-level of the project and running:
 
@@ -22,7 +24,8 @@ Every time you wish to run commands in this project, you will need to make sure
 
 This sets the environment variables related to this project and creates visability to the scripts in the flow directory. 
 
-## Updating Subrepositories
+### Updating Subrepositories
+---
 
 Once you have run a `source set_env.sh` in your current terminal, you are then able to update all your repositories to their latest version by running:
 
@@ -30,16 +33,23 @@ Once you have run a `source set_env.sh` in your current terminal, you are then a
 
 This runs a git pull on all repositories in your project.
 
-# Project Structure
+## Project Structure
+---
 
 The core of the SoC is NanoSoC. This is an example, configurable system that is the main framework. It has many different memory-mapped regions, one of which is designed for the connection of accelerator subsystems called the expansion region.
 
 The expansion region is able to instantiate an accelerator_subsystem by default. This means that anyone using NanoSoC as a platform for accelerator experimentation will need to build an `accelerator_subsystem` rtl module.
 
+### Accelerator Subsystem
+---
 `accelerator_subsystem` can either directly contain an accelerator (or multiple) or can instantiate accelerator wrappers which in turn instantiate accelerators.
 
 This module is expected to be found in `system/src/accelerator_subsystem.v`.
 
+### Accelerator Wrapper
+---
+Accelerator wrappers are located in `wrapper/src`. These should instantiate accelerators and can use wrapper components within the `accelerator_wrapper_tech` repository to allow a conversion of valid//ready interfaces to a memory-mapped AHB interface.
+
 ## Running the simulation
 
 This design instantiates a custom (AMBA-AHB) wrapper around the AES core to implement a memory-mapped 128-bit AES encrypt/decrypt accelerator that can be used as a software-driven peripheral or a semi-autonomous DMA subystem when 128-bit keys and variable length data payloads can be set up as scatter/gather descriptor chains for background processing.