fix a few typos (#2568)

doc/builder.md

@@ -332,7 +332,7 @@ pattern:
 
 ### Customization
 
-If you want to serialize a value in a custome way, you can do it with a
+If you want to serialize a value in a custom way, you can do it with a
 `tag_invoke` specialization like the following example which will map
 the year attribute to a string.
 
@@ -363,4 +363,4 @@ void tag_invoke(serialize_tag, builder_type &builder, const Car& car) {
 }
 
 } // namespace simdjson
-```
+```

doc/compile_time.md

@@ -128,7 +128,7 @@ Let us consider this example:
 ```
 
 You might want to ensure that the result is an array of persons. You can define your
-expection with concepts like so:
+expectation with concepts like so:
 
 ```cpp
 template <typename T>

include/simdjson/generic/ondemand/value.h

@@ -814,7 +814,7 @@ public:
    * in question is large. The fact that the extra code is there also bumps the executable size.
    *
    * We default operator[] on find_field_unordered() for convenience.
-   * It is the defaul because it would be highly surprising (and hard to debug) if the
+   * It is the default because it would be highly surprising (and hard to debug) if the
    * default behavior failed to look up a field just because it was in the wrong order--and many
    * APIs assume this. Therefore, you must be explicit if you want to treat objects as out of order.
    *

include/simdjson/padded_string.h

@@ -131,7 +131,7 @@ struct padded_string final {
   /**
    * This function accepts a wide string path (UTF-16) and converts it to
    * UTF-8 before loading the file. This allows windows users to work
-   * with unicode file paths without manually converting the paths everytime.
+   * with unicode file paths without manually converting the paths every time.
    *
    * @return IO_ERROR on error, including conversion failures.
    *