update-README.md (#931)

* changed 'module' to 'product'
* removed typo
Co-authored-by: Rahul Lugun <rlugun65@gmail,com>

Author: Rahul2044

test/README.md

@@ -66,12 +66,16 @@ deactivate
 ## Adding new tests: CVE mapping tests
 * You can see the code for scanner tests in ['test/test_scanner.py'](https://github.com/intel/cve-bin-tool/blob/master/test/test_scanner.py)
 * You can see checker wise test data in ['test/test_data'](https://github.com/intel/cve-bin-tool/blob/master/test/test_data)
-* If you just want to add a new mapping test for a checker, add a dictionary of *module*, *version* and *version_strings* in the mapping_test_data list . Here, *version_strings* are the list of strings that contain version signature or strings that commonly can be found in the module. For example: this is how the current mapping_test_data for gnutls look like. You should add the details of the new test case data at the end of `mapping_test_data` list:
+* If you just want to add a new mapping test for a checker, add a dictionary of *product*, *version* and *version_strings* in the mapping_test_data list . Here, *version_strings* are the list of strings that contain version signature or strings that commonly can be found in the module. For example: this is how the current mapping_test_data for gnutls look like. You should add the details of the new test case data at the end of `mapping_test_data` list:
 ```python
 mapping_test_data = [
-    {"module": "gnutls", "version": "2.1.6", "version_strings": ["gnutls-cli 2.1.6"]},
     {
-        "module": "gnutls",
+        "product": "gnutls", 
+        "version": "2.1.6", 
+        "version_strings": ["gnutls-cli 2.1.6"]
+    },
+    {
+        "product": "gnutls",
         "version": "2.3.11",
         "version_strings": ["gnutls-serv 2.3.11"],
     },
@@ -85,9 +89,9 @@ mapping_test_data = [
 
 To make the basic test suite run quickly, we create "faked" binary files to test the **CVE mappings**.  However, we want to be able to test real files to test that the **signatures** work on real-world data.
 
-You can see test data for package tests in package_test_data varible of the test data file you are writing test for.
+You can see test data for package tests in *package_test_data* varible of the test data file you are writing test for.
 
-We have `test_version_in_package` function in `test_scanner` that takes a url, and package name, module name and a version, and downloads the package, runs the scanner against it, and makes sure it is the package that you've specified. But we need more tests!
+We have `test_version_in_package` function in `test_scanner` that takes a *url*, and *package name*, *module name* and a *version*, and downloads the package, runs the scanner against it, and makes sure it is the package that you've specified. But we need more tests!
 
 * To add a new test, find an appropriate publicly available file (linux distribution packages and public releases of the packages itself are ideal). You should add the details of the new test case in the `package_test_data` variable of the file for which you are writing test for. For example: this is how the current package_test_data for binutils look like. You should add the details of the new test case data at the end of `package_test_data` list:
 
@@ -96,13 +100,13 @@ package_test_data = [
     {
         "url": "http://security.ubuntu.com/ubuntu/pool/main/b/binutils/",
         "package_name": "binutils_2.26.1-1ubuntu1~16.04.8_amd64.deb",
-        "module": "binutils",
+        "product": "binutils",
         "version": "2.26.1",
     },
     {
         "url": "http://mirror.centos.org/centos/7/os/x86_64/Packages/",
         "package_name": "binutils-2.27-43.base.el7.x86_64.rpm",
-        "module": "binutils",
+        "product": "binutils",
         "version": "2.27",
     },
 ]