Fix links refering to non-existing pages

Author: WojciechMazur

docs/_docs/reference/contextual/context-bounds.md

@@ -47,7 +47,7 @@ Since the context parameter now has a name, it can be referred
 to in the body of `reduce`. An example is the `m.unit` reference in the definition above.
 
 If the context bound does not carry an `as` clause, the generated witness parameter gets a compiler-synthesized name. However, a [currently experimental
-language extension](../experimental/default-names-context-bounds.md) would in this case give the context parameter the same name as the bound type parameter.
+language extension](../experimental/typeclasses.md#better-default-names-for-context-bounds) would in this case give the context parameter the same name as the bound type parameter.
 
 Named context bounds were introduced in Scala 3.6.
 

docs/_docs/reference/experimental/typeclasses.md

@@ -25,7 +25,7 @@ in source version `future` if the additional experimental language import `modul
 ```
 
 It is intended to turn features described here into proposals under the Scala improvement process. A first installment is SIP 64, which covers some syntactic changes, names for context bounds, multiple context bounds and deferred givens. This SIP has been accepted for inclusion in the language and will be released in Scala 3.6. The remaining elements
-that concern type classes are described in the following. There is also a separate [page on modularity improvements](../modularity.md) that describes proposed additions not directly related to type classes.
+that concern type classes are described in the following. There is also a separate [page on modularity improvements](modularity.md) that describes proposed additions not directly related to type classes.
 
 ## Generalizing Context Bounds
 

docs/_docs/reference/features-classification.md

@@ -40,7 +40,7 @@ These constructs replace existing constructs with the aim of making the language
  - [Extension methods](contextual/extension-methods.md) replace implicit classes with a clearer and simpler mechanism.
  - [Opaque type aliases](other-new-features/opaques.md) replace most uses
    of value classes while guaranteeing absence of boxing.
- - [Top-level definitions](dropped-features/package-objects.md) replace package objects, dropping syntactic boilerplate.
+ - [Top-level definitions](other-new-features/toplevel-definitions.md) replace package objects, dropping syntactic boilerplate.
  - [Export clauses](other-new-features/export.md)
  provide a simple and general way to express aggregation, which can replace the
  previous facade pattern of package objects inheriting from classes.

docs/_docs/reference/overview.md

@@ -46,7 +46,7 @@ These constructs replace existing constructs with the aim of making the language
   replace implicit classes with a clearer and simpler mechanism.
 - [Opaque type aliases](other-new-features/opaques.md)
   replace most uses of value classes while guaranteeing the absence of boxing.
-- [Top-level definitions](dropped-features/package-objects.md)
+- [Top-level definitions](other-new-features/toplevel-definitions.md)
   replace package objects, dropping syntactic boilerplate.
 - [Export clauses](other-new-features/export.md)
   provide a simple and general way to express aggregation, which can replace