Update README_validations.md with Dave's feedback around correctness.

Co-authored-by: David Waltermire <david.waltermire@nist.gov>

README_validations.md

@@ -109,7 +109,7 @@ You should validate OSCAL documents saved to files to ensure it will work for th
 
 ## What does validation *not* tell me?
 
-The rules expressed and enforced by a schema are limited to those that can systematically be checked by automated processes. Valid OSCAL documents are *not necessarily* "correct". For OSCAL, validation is an objective determination by program, whereas correct is a subjective determination of analysis by a person. Validataion ensures only that *your data is fit for further processing*; such processing can include operations to determine the data's correctness, completeness, adequacy, veracity, or anything else not defined or definable by a schema. 
+The rules expressed and enforced by a schema are limited to those that can be systematically checked by automated processes. Valid OSCAL documents are *not necessarily* "correct" from an information perspective. For OSCAL, validation is an objective determination by a program, whereas correct is a subjective determination based on analysis by a person to determine if the information contained in the content is appropriate by some measure. Validation ensures only that *your data is fit for further processing*; such processing can include operations to determine the data's correctness, completeness, adequacy, veracity, or anything else not defined or definable by a schema. 
 
 ## Other ways to validate?