Apply suggestions from code review

Co-authored-by: Adam Leventhal <[email protected]>

Author: anelson

typify-impl/src/test_util.rs

@@ -73,7 +73,7 @@ fn validate_output_impl<T: JsonSchema + Schema>(ignore_variant_names: bool) {
 
     let expected = T::schema();
 
-    // A few test cases use structs that use the fully-qualified path to a std type like
+    // A few test cases use structs that use the fully-qualified path to a std type such as
     // `::std::collections::HashMap`.  Decanonicalize those types so that later in this function
     // when we also decanonicalize the types generated by typify, we can compare the two and expect
     // their ASTs to match exactly
@@ -104,18 +104,16 @@ fn validate_output_impl<T: JsonSchema + Schema>(ignore_variant_names: bool) {
 /// is reasonable to expect that the generated Rust binding matches exactly the Rust type from
 /// which the JSON Schema was generated.
 ///
-/// The code generation logic that generates Rust bindings given JSON Schema always canonicalizes
+/// Our code generation logic, always canonicalizes
 /// any standard type (eg, `Option` is output as `::std::option::Option`), to avoid potential
 /// conflicts with types in the JSON schema with conflicting names like `Option`.  Unfortunately,
-/// this complicates the test cases that start with a Rust type that implements `JsonSchema`, use
-/// that to generate a JSON schema for that type, then use typify to generate a Rust binding for
-/// that type, and expects that the Rust AST for the source type and the generated type are exactly
-/// the same.
+/// this complicates the test cases that validate that a round-trip from Rust to JSON back to Rust
+/// are exactly the same.
 ///
 /// To work around this, this somewhat inelegant function simply finds every type in the input AST
 /// that starts with `::std`, and strips everything but the simple type name.  This will break if
-/// any of the input Rust types ever use fully-qualified type names that start with `::std`, but
-/// the solution is to simply not do that :)
+/// any of the input Rust types use fully-qualified type names that start with `::std`, but
+/// the solution is to simply not do that.
 fn decanonicalize_std_types(mut input: DeriveInput) -> DeriveInput {
     struct Visitor;