diff --git a/README.md b/README.md
index babc4e8055d822d5e5dedeec1df44106583ae596..a2dd6fbbd7ba55453c25043269a7cebc469a97ae 100644
--- a/README.md
+++ b/README.md
@@ -1,40 +1,38 @@
 # Accelerator System Top-Level
 
-This repo is the top-level repository which contains accelerator and SoC Labs provided design IP in forms of git subrepositories.
+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.
 
 The SoC wiring is handled in this repository too, along with design and verification for accelerator wrappers.
 
-## Creating own top-level
+## Re-creating the top-level design
 
-The first stage of putting your accelerator into a SoC is to build the accelerator in your own repository. 
+To build this example reference design, the design and sub-modules must be cloned *with* --recursive flag:
 
-Once you have a custom design repository, you are able to fork the template System Top-level repository and make some changes.
+  `git clone --recursive https://git.soton.ac.uk/soclabs/accelerator-project-secworks-aes-128.git`
 
-After forking, you need to add your own repository as a submodule. The first thing to do is to clone your new forked top-level.
+  Then at the top level of this project import the 3rd-party IP AES engine to the suitably named sub-directory:
+ 
+  `git clone https://github.com/secworks/aes.git secworks-aes`
 
-## Cloning 
+  Then set up the environment variables and paths:
+  
+  `source set_env.sh` 
 
-To clone this repository and its subrepository, use the following command:
+This sets the environment variables related to this project and creates visability to the scripts in the flow directory. Because of this, you can now run:
 
-`git clone --recusrive $REPO_NAME`
-
-Once the repository and the subrepository has been cloned, the next stage is to initalise the environment variables and check out the sub repositories to a branch.
-
-First navigate to the top of this cloned repository and run:
-
-`source set_env.sh` 
+`soc-init`
 
-This sets the environment variables related to this project and creates visability to the scripts in the flow directory. Because of this, you scan now run:
+## Running the simulation
 
-`soc-init`
+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.
 
-This checks out all the repositories to the `main` branch. You are then able to check out the sub repos to the desired branches.
+To run the simulation the 'socsim' command executes the makefile in the 'nanosoc_tech' microcontroller framework. (Edit the simulator target in nanosoc_tech/system/makefile for the simulator EDA tool used). Then use the 
 
-## Adding Submodule
+  `socsim system_secworks_aes128 TESTNAME=aes128_tests`
 
-After setting up your workarea, you now need to add your accelerator design repository as a subrepo.
+This runs the integration test program on the Arm Cortex-M0 processor using the 'system_secworks_aes128.sh' script provided in the simulate/socsim directoty and the logs are produced in the simulate/sim/system_secworks_aes128/logs directory.
 
-From `$DESIGN_ROOT`, you are able to run:
+To add the secworks-aes IP as a managed git sub-module:
 
 `git submodule status`