fixed typos and paths for arch_test readme (#638)

Co-authored-by: Neel Gala <neelgala@incoresemi.com>

arch_test_target/spike/README.md

@@ -15,11 +15,10 @@ The [README.md](../README.md) at the top level of the riscv-isa-sim directory gi
 Also at the top level is an ``arch_test_target directory``. This directory contains all the collaterals
 required to add Spike as a target to the architectural test framework.
 
-The user will have to modify the ``TARGETDIR`` variable in ``arch_test_target/spike/Makfile.include`` to point to the
-absolute address of the ``riscv-isa-sim/arch_test_target``. 
-
-The user can also modify the ``XLEN`` variable based on whether 32-bit or 64-bit tests need to be run.
-If you would like to run tests of a single extension then set the `RISCV_DEVICE` to that extension
+The file ``arch_test_target/spike/Makefile.include`` contains various parameters which can be set by 
+the user to modify the instance of spike on which the tests need to be run.
+The user can modify the ``XLEN`` variable based on whether 32-bit or 64-bit tests need to be run.
+If one would like to run tests of a single extension then set the `RISCV_DEVICE` to that extension
 name (eg. M, C, Zifencei, etc). Leaving the ``RISCV_DEVICE`` empty would indicate running all tests
 for all extensions available in the ``device/rv{XLEN}i_m`` directory No other variables should be modified.
 
@@ -31,6 +30,9 @@ Now clone the architectural test framework repo and copy the updated Makefile.in
   $ 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
+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:
 
 ```