replace old compliance name with new arch-test name in spike target README (#690)

1 files changed, 6 insertions, 6 deletions

diff --git a/arch_test_target/spike/README.md b/arch_test_target/spike/README.md
index f294ccb..7618dc3 100644
--- a/arch_test_target/spike/README.md
+++ b/arch_test_target/spike/README.md
@@ -4,7 +4,7 @@ This is a reference for running Spike as a target for the RISC-V Architectural T
 
 ## Getting Spike
 
-The Spike repository should be cloned from [here](https://github.com/riscv/riscv-isa-sim/), preferably at the same directory level as the riscv-compliance repository.
+The Spike repository should be cloned from [here](https://github.com/riscv/riscv-isa-sim/), preferably at the same directory level as the riscv-arch-test repository.
 
 ## Building Spike
 
@@ -25,15 +25,15 @@ for all extensions available in the ``device/rv{XLEN}i_m`` directory No other va
 Now clone the architectural test framework repo and copy the updated Makefile.include to it:
 
 ```
-  $ git clone https://github.com/riscv/riscv-compliance.git
-  $ cd riscv-compliance
+  $ git clone https://github.com/riscv/riscv-arch-test.git
+  $ cd riscv-arch-test
   $ cp <custom-path>/riscv-isa-sim/arch_test_target/Makefile.include .
 ```
 
-The user will have to modify the ``TARGETDIR`` variable in ``riscv-compliance/Makefile.include`` to point to the
+The user will have to modify the ``TARGETDIR`` variable in ``riscv-arch-test/Makefile.include`` to point to the
 absolute location of the ``riscv-isa-sim/arch_test_target`` directory. 
 
-You can execute the tests from the root directory of the riscv-compliance repo:
+You can execute the tests from the root directory of the riscv-arch-test repo:
 
 ```
 make compile simulate verify
@@ -42,7 +42,7 @@ make compile simulate verify
 ## Updating the target for new tests
 
 As tests for new extensions are added to the architectural test repo, the spike target (i.e.
-arch_test_target directory) will also need to be updated accordingly. Please refer to the [Porting a new target](https://github.com/riscv/riscv-compliance/blob/master/doc/README.adoc#5-porting-a-new-target)
+arch_test_target directory) will also need to be updated accordingly. Please refer to the [Porting a new target](https://github.com/riscv/riscv-arch-test/blob/master/doc/README.adoc#5-porting-a-new-target)
 section for more details on what those changes/updates should be.