CDM-88 Some docs updates

Author: pravinbhat

README.md

@@ -94,15 +94,15 @@ Each line above represents a partition-range (`min,max`). Alternatively, you can
 
 ```
 spark-submit --properties-file cdm.properties /
- --conf spark.cdm.schema.origin.keyspaceTable="test_ks.cat_promo" /
+ --conf spark.cdm.schema.origin.keyspaceTable="<keyspace-name>.<table-name>" /
  --conf spark.tokenRange.partitionFile="/<path-to-file>.<csv-input-filename>" /
  --master "local[*]" /
  --class com.datastax.cdm.job.<Migrate|DiffData> cassandra-data-migrator-4.x.x.jar &> logfile_name_$(date +%Y%m%d_%H_%M).txt
 ```
 This mode is specifically useful to processes a subset of partition-ranges that may have failed during a previous run.
 
 > **Note:**
-> A file named `./<keyspace>.<tablename>_partitions.csv` will be auto created by the Migration & Validation job in the above format containing any failed partition ranges. You can use this file as an input to process any failed partition in a following run.
+> A file named `./<keyspace>.<tablename>_partitions.csv` is auto generated by the Migration & Validation jobs in the above format containing any failed partition ranges. No file is created if there are no failed partitions. You can use this file as an input to process any failed partition in a following run.
 
 # Perform large-field Guardrail violation checks
 - The tool can be used to identify large fields from a table that may break you cluster guardrails (e.g. AstraDB has a 10MB limit for a single large field)  `--class com.datastax.cdm.job.GuardrailCheck` as shown below