Fix links

Author: jack-berg

docs/knowledge/api-design.md

@@ -80,7 +80,7 @@ unambiguously.
 ### Runtime / instrumentation-time boundaries (Span methods, metric recordings, log builders)
 
 Do **not** throw. Log the violation via
-[`ApiUsageLogger`](../../common/src/main/java/io/opentelemetry/common/ApiUsageLogger.java) —
+[`ApiUsageLogger`](../../common/src/main/java/io/opentelemetry/common/impl/ApiUsageLogger.java) —
 which logs at `FINEST` with a stack trace so the offending call site is visible — then degrade
 gracefully (return `this`, an empty/noop result, or substitute a safe default such as
 `Attributes.empty()` or `Context.current()`):

docs/knowledge/build.md

@@ -25,7 +25,7 @@ All tasks can be scoped to a single module by prefixing with the module path:
 
 `./gradlew build` and `./gradlew check` both depend on the `jApiCmp` task, which compares the
 locally-built jars against the latest release and writes diffs to `docs/apidiffs/current_vs_latest/`.
-Include any changes to those files in your PR. See [api-stability.md](api-stability.md#japicmp)
+Include any changes to those files in your PR. See [api-stability.md](api-design.md#japicmp)
 for details.
 
 If your branch is not up to date with `main`, `jApiCmp` may produce a diff that reflects changes