Repository: MicrochipTech/cryptoauthlib (language: python)

Issue:
typo fix
fix typo

# Please describe the purpose of this pull request



# Checklist
* [x] I have reviewed the [CONTRIBUTING.md](https://github.com/MicrochipTech/cryptoauthlib/blob/main/CONTRIBUTING.md) and agree to it's terms

dead link - test readme
There is a link to test readme here - https://github.com/MicrochipTech/cryptoauthlib#tests

But there is no readme file in that location


Discussion / hints:

Fix patch:
diff --git a/README.md b/README.md
index a57f1c2a3..51a6c37d8 100644
--- a/README.md
+++ b/README.md
@@ -104,7 +104,7 @@ Host Device Support
 ---------------
 
 CryptoAuthLib will run on a variety of platforms from small micro-controllers
-to desktop host systems. See [hal readme](lib/hal/readme.md)
+to desktop host systems. See [hal readme](lib/hal/README.md)
 
 If you have specific microcontrollers or platforms you need support
 for, please contact us through the Microchip portal with your request.
diff --git a/python/README.md b/python/README.md
index b41206423..30af233a2 100644
--- a/python/README.md
+++ b/python/README.md
@@ -105,7 +105,7 @@ print(''.join(['%02X ' % x for x in randomnum]))
 ```
 
 In the above python code, "import cryptoauthlib" imports the python module. load_cryptoauthlib()
-function loads the ompiled library. The load_cryptoauthlib() is a function that you will not
+function loads the compiled library. The load_cryptoauthlib() is a function that you will not
 see in the 'C' library, this is a python specific utility function and is required for python
 scripts to locate and load the compiled library.
 


Test patch:
diff --git a/test/README.md b/test/README.md
new file mode 100644
index 000000000..e591ea511
--- /dev/null
+++ b/test/README.md
@@ -0,0 +1,163 @@
+Cryptoauthlib Test Application
+===============================================================================
+
+The test application for cryptoauthlib provides tests and utilities for the
+library and connected devices. It can be built and used both as an interactive
+application or by individual command lines.
+
+Platforms supported by CMake
+-------------------------------------------------------------------------------
+The test application can be configured for the following platforms by invoking
+CMake:
+
+* Windows
+* Linux
+* MacOs
+* Zephyr
+
+Enable the BUILD_TESTS option either in your CMakeLists.txt file that includes
+cryptoauthlib or otherwise on the command line when you invoke CMake
+
+Embedded Platforms
+-------------------------------------------------------------------------------
+The test application can also be added and configured if you use the following
+software platforms:
+
+### Harmony 3
+
+Add the cryptoauthlib test application component to the component graph. The
+test application depends on stdio being available so you also need to include
+the stdio component which you will connect to an available uart.
+
+
+Invoking the test application
+-------------------------------------------------------------------------------
+
+The test application can be run both as a command line application as well as
+interactively. The default mode is interactive. 
+
+### Embedded
+
+#### Interactive
+The function `atca_test_task` is a non returning function that waits for
+characters from a stdin implementation. If the system supports scanf this can
+be used to create a test application rtos task - if there are no parallel tasks
+to be executed in the system then one can forgo an RTOS and simply call this
+function from the main function after board initialization is complete
+
+#### Either interactive or "command line" using a custom runner
+Alternatively the function `processCmd` will accept a buffer for parsing and
+execution. The buffer has to be a complete command however so ensure that the
+calling code properly accumulates all need characters into the buffer first
+
+### Platforms with a shell
+
+#### Interactive
+
+Launch the `cryptoauth_test` application from the build directory
+
+#### Command line
+
+Launch the `cryptoauth_test` application with command line arguments
+
+```
+build> ./cryptoauth_test <command> -d <device> -i <interface> [<interface options>] 
+```
+
+For example to retrieve the device serial number from a [Cryptoauth Trust Platform Development Kit](https://www.microchip.com/en-us/development-tool/DM320118)
+
+```
+./cryptoauth_test sernum -d ecc608 -i hid i2c -a 0x6C
+```
+
+Commands
+-------------------------------------------------------------------------------
+
+### Device Selection
+* sha204 - Select ATSHA204/A
+* sha206 - Select ATSHA206A
+* ecc108 - Select ATECC108A
+* ecc204 - Select ECC204
+* ecc508 - Select ATECC508A
+* ecc608 - Select ATECC608A/B
+* ta100  - Select TA100
+
+### Utilities
+* info - Read the device revision data
+* sernum - Read the device serial number
+* readcfg - Read the configuration memory
+* lockstat - Read the lock status for each memory region
+* rand - Generate 32 bytes of random data from the device's RNG by executing
+    atcab_random (many devices return a constant value if the configuration is 
+    not 'locked')
+* lockcfg - Sets the device configuration lock by executing atcab_lock_config_zone
+* lockdata - Sets the device data/setup lock by executing atcab_lock_data_zone
+
+### Software API Testing
+* cd - Run the compressed certificate library (atcacert_) unit tests
+* util - Run utility unit tests
+
+### Device API Testing
+* basic - Run (atcab_) API validation tests
+* cio - Run compressed certificate library (atcacert_) device integration tests
+
+### Cryptographic Library
+* crypto - Run software library API tests (validate host cryptographic functions) 
+* crypto_int - Run device integration tests for supported libraries
+* pbkdf2 - Run pbkdf2 algorithm tests (host and device)
+
+### ECC608 Specific Commands
+* clkdivm0 - Sets the ECC608 clock divider to 0x00
+* clkdivm1 - Sets the ECC608 clock divider to 0x05
+* clkdivm2 - Sets the ECC608 clock divider to 0x0D
+
+### TA100 Specific Commands
+* handles - Prints the ta100 handle information for all created handles
+* talib - Run (talib_) API validation tests
+
+
+Options
+-------------------------------------------------------------------------------
+
+### -i (Device)
+
+Usage: `-i <device_type>`
+
+Selects the device type - per the device list that you would otherwise see when
+invoking `help` from the menu. Possible options if the corresponding `ATCA_<device>_SUPPORT`
+macro is enabled:
+
+* sha204
+* sha206
+* ecc108
+* ecc204
+* ecc508
+* ecc608
+* ta100
+
+
+### -i (Interface)
+
+Usage: `-i <interface_type> <interface parameters>`
+
+Selects the interface type that will be used to communicate with the device.
+Additional parameters can be used to alter the defaults for the interface
+
+* hid <i2c/swi/spi> <i2c_bus_id>
+* i2c <i2c_bus_id>
+* spi <spi_bus_id> <select_pin> <baud_rate>
+* uart <uart_port> <uart_baud> <uart_wordsize> <uart_stopbits> <uart_parity>
+
+Notes:
+* Uart port is an integer on windows platforms (specify 11 for COM11) and a
+  string on linux/macos platforms (e.g. "/dev/ttyACM0")
+
+### -a (Address)
+
+Usage: `-a <device_address>`
+
+### -y (Quiet)
+
+Usage: `-y`
+
+Silence prompts with an implicit agreement