fix: links broke after a heading change (#4696)

Author: zamulla

docs/topics/booleans.md

@@ -40,6 +40,6 @@ The `||` and `&&` operators work lazily, which means:
 * If the first operand is `true`, the `||` operator does not evaluate the second operand.
 * If the first operand is `false`, the `&&` operator does not evaluate the second operand.
 
-> On the JVM, nullable references to boolean objects are boxed in Java classes, just like with [numbers](numbers.md#numbers-representation-on-the-jvm).
+> On the JVM, nullable references to boolean objects are boxed in Java classes, just like with [numbers](numbers.md#boxing-and-caching-numbers-on-the-java-virtual-machine).
 >
 {style="note"}

docs/topics/characters.md

@@ -36,7 +36,7 @@ fun main() {
 
 If a value of character variable is a digit, you can explicitly convert it to an `Int` number using the [`digitToInt()`](https://kotlinlang.org/api/latest/jvm/stdlib/kotlin.text/digit-to-int.html) function.
 
-> On the JVM, characters are boxed in Java classes when a nullable reference is needed, just like with [numbers](numbers.md#numbers-representation-on-the-jvm).
+> On the JVM, characters are boxed in Java classes when a nullable reference is needed, just like with [numbers](numbers.md#boxing-and-caching-numbers-on-the-java-virtual-machine).
 > Identity is not preserved by the boxing operation.
 >
 {style="note"}

docs/topics/inline-classes.md

@@ -100,7 +100,7 @@ other classes and are always `final`.
 
 In generated code, the Kotlin compiler keeps a *wrapper* for each inline class. Inline class instances can be represented 
 at runtime either as wrappers or as the underlying type. This is similar to how `Int` can be 
-[represented](numbers.md#numbers-representation-on-the-jvm) either as a primitive `int` or as the wrapper `Integer`.
+[represented](numbers.md#boxing-and-caching-numbers-on-the-java-virtual-machine) either as a primitive `int` or as the wrapper `Integer`.
 
 The Kotlin compiler will prefer using underlying types instead of wrappers to produce the most performant and optimized code. 
 However, sometimes it is necessary to keep wrappers around. As a rule of thumb, inline classes are boxed whenever they