fix typos

xso-proc/src/field/child.rs

@@ -338,7 +338,7 @@ impl ExtractDef {
             // thing no matter whether the extracted field is of type
             // `Option<T>` or `T`.
             //
-            // And then, type inferrence does the rest: There is ambiguity
+            // And then, type inference does the rest: There is ambiguity
             // there, of course, if we call `.into()` on a value of type
             // `Option<T>`: Should Rust wrap it into another layer of
             // `Option`, or should it just move the value? The answer lies in

xso-proc/src/field/mod.rs

@@ -235,7 +235,7 @@ fn default_name(span: Span, name: Option<NameRef>, field_ident: Option<&Ident>)
 /// `field_ident` is, for some field types, used to infer an XML name if
 /// it is not specified explicitly.
 ///
-/// `field_ty` is needed for type inferrence on extracted fields.
+/// `field_ty` is needed for type inference on extracted fields.
 ///
 /// `container_namespace` is used in some cases to insert a default
 /// namespace.

xso-proc/src/meta.rs

@@ -475,7 +475,7 @@ impl XmlCompoundMeta {
 /// in case parsing the type path does then fail.
 fn maybe_type_path(p: parse::ParseStream<'_>) -> (bool, Option<Span>) {
     // ParseStream cursors do not advance the stream, but they are also rather
-    // unwieldly to use. Prepare for a lot of `let .. = ..`.
+    // unwieldy to use. Prepare for a lot of `let .. = ..`.
 
     let cursor = if p.peek(token::PathSep) {
         // If we have a path separator, we need to skip that initially. We

xso-proc/src/types.rs

@@ -299,7 +299,7 @@ pub(crate) fn as_xml_text_fn(ty: Type) -> Expr {
 }
 
 /// Construct a [`syn::Path`] referring to `::xso::TextCodec::<#for_ty>`,
-/// returing the span of `for_ty` alongside it.
+/// returning the span of `for_ty` alongside it.
 fn text_codec_of(for_ty: Type) -> (Span, Path) {
     let span = for_ty.span();
     (