Update markdown files for preprocessing purposes

Author: BarkingBad

docs/docs/reference/changed-features.md

@@ -0,0 +1,9 @@
+---
+title: "Other Changed Features"
+type: chapter
+num: 51
+previous-page: /scala3/reference/other-new-features/type-test
+next-page: /scala3/reference/changed-features/numeric-literals
+---
+
+The following pages document the features that have changed in Scala 3, compared to Scala 2.

docs/docs/reference/changed-features/compiler-plugins.md

@@ -1,7 +1,9 @@
 ---
-layout: doc-page
 title: "Changes in Compiler Plugins"
-movedTo: https://docs.scala-lang.org/scala3/reference/changed-features/compiler-plugins.html
+type: section
+num: 67
+previous-page: /scala3/reference/changed-features/eta-expansion
+next-page: /scala3/reference/changed-features/lazy-vals-init
 ---
 
 Compiler plugins are supported by Dotty (and Scala 3) since 0.9. There are two notable changes

docs/docs/reference/changed-features/eta-expansion-spec.md

@@ -1,7 +1,7 @@
 ---
-layout: doc-page
+layout: singlepage-overview
+scala3: true
 title: "Automatic Eta Expansion - More Details"
-movedTo: https://docs.scala-lang.org/scala3/reference/changed-features/eta-expansion-spec.html
 ---
 
 ## Motivation

docs/docs/reference/changed-features/eta-expansion.md

@@ -1,7 +1,9 @@
 ---
-layout: doc-page
 title: "Automatic Eta Expansion"
-movedTo: https://docs.scala-lang.org/scala3/reference/changed-features/eta-expansion.html
+type: section
+num: 66
+previous-page: /scala3/reference/changed-features/pattern-matching
+next-page: /scala3/reference/changed-features/compiler-plugins
 ---
 
 The conversion of _methods_ into _functions_ has been improved and happens automatically for methods with one or more parameters.
@@ -36,7 +38,7 @@ rather than `next _`.
 The reason for excluding nullary methods from automatic eta expansion
 is that Scala implicitly inserts the `()` argument, which would
 conflict with eta expansion. Automatic `()` insertion is
-[limited](../dropped-features/auto-apply.md) in Scala 3, but the fundamental ambiguity
+[limited](../dropped-features/auto-apply.html) in Scala 3, but the fundamental ambiguity
 remains.
 
-[More details](eta-expansion-spec.md)
+[More details](eta-expansion-spec.html)

docs/docs/reference/changed-features/implicit-conversions-spec.md

@@ -1,7 +1,7 @@
 ---
-layout: doc-page
+layout: singlepage-overview
+scala3: true
 title: "Implicit Conversions - More Details"
-movedTo: https://docs.scala-lang.org/scala3/reference/changed-features/implicit-conversions-spec.html
 ---
 
 ## Implementation
@@ -82,7 +82,7 @@ implicit val myConverter: Int => String = _.toString
 implicit val myConverter: Conversion[Int, String] = _.toString
 ```
 
-Note that implicit conversions are also affected by the [changes to implicit resolution](implicit-resolution.md) between Scala 2 and Scala 3.
+Note that implicit conversions are also affected by the [changes to implicit resolution](implicit-resolution.html) between Scala 2 and Scala 3.
 
 ## Motivation for the changes
 
@@ -109,9 +109,9 @@ will report a type error, because `Map` isn't an instance of
 Implicit values that are used as views should see their type changed to `Conversion`.
 
 For the migration of implicit conversions that are affected by the
-changes to implicit resolution, refer to the [Changes in Implicit Resolution](implicit-resolution.md) for more information.
+changes to implicit resolution, refer to the [Changes in Implicit Resolution](implicit-resolution.html) for more information.
 
 ## Reference
 
-For more information about implicit resolution, see [Changes in Implicit Resolution](implicit-resolution.md).
+For more information about implicit resolution, see [Changes in Implicit Resolution](implicit-resolution.html).
 Other details are available in [PR #2065](https://github.com/lampepfl/dotty/pull/2065).

docs/docs/reference/changed-features/implicit-conversions.md

@@ -1,7 +1,9 @@
 ---
-layout: doc-page
 title: "Implicit Conversions"
-movedTo: https://docs.scala-lang.org/scala3/reference/changed-features/implicit-conversions.html
+type: section
+num: 60
+previous-page: /scala3/reference/changed-features/implicit-resolution
+next-page: /scala3/reference/changed-features/overload-resolution
 ---
 
 An _implicit conversion_, also called _view_, is a conversion that
@@ -61,4 +63,4 @@ implicitly[Ordering[A]] // Ok, will use the implicit conversion from
                         // `A` to `Int` and the `Ordering` for `Int`.
 ```
 
-[More details](implicit-conversions-spec.md)
+[More details](implicit-conversions-spec.html)

docs/docs/reference/changed-features/implicit-resolution.md

@@ -1,8 +1,11 @@
 ---
-layout: doc-page
 title: "Changes in Implicit Resolution"
-movedTo: https://docs.scala-lang.org/scala3/reference/changed-features/implicit-resolution.html
+type: section
+num: 59
+previous-page: /scala3/reference/changed-features/type-inference
+next-page: /scala3/reference/changed-features/implicit-conversions
 ---
+
 This section describes changes to the implicit resolution that apply both to the new `given`s and to the old-style `implicit`s in Scala 3.
 Implicit resolution uses a new algorithm which caches implicit results
 more aggressively for performance. There are also some changes that

docs/docs/reference/changed-features/imports.md

@@ -1,7 +1,9 @@
 ---
-layout: doc-page
 title: "Imports"
-movedTo: https://docs.scala-lang.org/scala3/reference/changed-features/imports.html
+type: section
+num: 56
+previous-page: /scala3/reference/changed-features/wildcards
+next-page: /scala3/reference/changed-features/type-checking
 ---
 
 The syntax of wildcard and renaming imports (and exports) has changed.

docs/docs/reference/changed-features/interpolation-escapes.md

@@ -1,7 +1,7 @@
 ---
-layout: doc-page
+layout: singlepage-overview
+scala3: true
 title: "Escapes in interpolations"
-movedTo: https://docs.scala-lang.org/scala3/reference/changed-features/interpolation-escapes.html
 ---
 
 In Scala 2 there is no straightforward way to represent a single quote character `"` in a single quoted interpolation. A `\` character can't be used for that because interpolators themselves decide how to handle escaping, so the parser doesn't know whether the `"` should be escaped or used as a terminator.

docs/docs/reference/changed-features/lazy-vals-init.md

@@ -1,7 +1,9 @@
 ---
-layout: doc-page
-title: Lazy Vals initialization
-movedTo: https://docs.scala-lang.org/scala3/reference/changed-features/lazy-vals-init.html
+title: Lazy Vals Initialization
+type: section
+num: 68
+previous-page: /scala3/reference/changed-features/compiler-plugins
+next-page: /scala3/reference/changed-features/main-functions
 ---
 
 Scala 3 implements [Version 6](https://docs.scala-lang.org/sips/improved-lazy-val-initialization.html#version-6---no-synchronization-on-this-and-concurrent-initialization-of-fields)