Minor doc issues seen in scalafmt update

ekrich · Jan 15, 2025 · c4e4da7 · c4e4da7
1 parent a3a11f7
commit c4e4da7
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/sconfig/shared/src/main/scala/org/ekrich/config/Config.scala b/sconfig/shared/src/main/scala/org/ekrich/config/Config.scala
@@ -62,7 +62,7 @@ import scala.annotation.varargs
  * [[ConfigUtil$.splitPath ConfigUtil.splitPath(String)]] to convert between
  * path expressions and individual path elements (keys).
  *
- * <p> Another difference between `Config} and `ConfigObject` is that
+ * <p> Another difference between `Config` and `ConfigObject` is that
  * conceptually, `ConfigValue`s with a [[ConfigValue#valueType valueType]] of
  * [[ConfigValueType#NULL NULL]] exist in a `ConfigObject`, while a `Config`
  * treats null values as if they were missing. (With the exception of two

diff --git a/sconfig/shared/src/main/scala/org/ekrich/config/ConfigMergeable.scala b/sconfig/shared/src/main/scala/org/ekrich/config/ConfigMergeable.scala
@@ -45,7 +45,7 @@ trait ConfigMergeable {
    * just return the original value, since they automatically override any
    * fallback. This means that objects do not merge "across" non-objects; if you
    * write `object.withFallback(nonObject).withFallback(otherObject)`, then
-   * `otherObject`will simply be ignored. This is an intentional part of how
+   * `otherObject` will simply be ignored. This is an intentional part of how
    * merging works, because non-objects such as strings and integers replace
    * (rather than merging with) any prior value:
    *