chore: fix some comments

CONTRIBUTING.md

@@ -198,7 +198,7 @@ short and inconsistent.
 
 > Why don't we use `latest` tags?
 
-`latest` tags require the commit that they point to to constantly change. The
+`latest` tags require the commit that they point to constantly change. The
 [official git docs on retagging][retagging] call this practice "insane". It
 causes problems for people's developer experience, but more importantly it
 makes builds inherently non-reproducible. There should be a guarantee of

artificer/DESIGN.md

@@ -78,10 +78,10 @@ out-dir/
 
 ```
 
-The special folder `.artificer-metadata` is reserved for artificer specfic metadata.
+The special folder `.artificer-metadata` is reserved for artificer specific metadata.
 Most importantly, the `out.lock` is a redundant copy of the main `artificer.lock`,
 which represents the state of the `out-dir`. This is important when, for example,
-the main lockfile is comitted in git and updates - we can use the lockfile in the
+the main lockfile is committed in git and updates - we can use the lockfile in the
 `out-dir` to know if any artifacts need to be extracted again.
 
 Note that `out.lock` does not hash the actual contents of the out-dir, as that would

seek-camera/sys/build.rs

@@ -89,7 +89,7 @@ fn main() -> Result<()> {
 #[derive(Debug)]
 struct MyParseCallbacks;
 impl ParseCallbacks for MyParseCallbacks {
-    /// Renames enum variants such that they are PascalCase and strips unecessary prefix.
+    /// Renames enum variants such that they are PascalCase and strips unnecessary prefix.
     fn enum_variant_name(
         &self,
         enum_name: Option<&str>,