Fix the layout part of the matchable.md

docs/docs/reference/other-new-features/matchable.md

@@ -1,3 +1,4 @@
+---
 layout: doc-page
 title: The Matchable Trait
 ---
@@ -12,21 +13,26 @@ arrays that is defined like this:
 ```scala
   opaque type IArray[+T] = Array[_ <: T]
 ```
+
 The `IArray` type offers extension methods for `length` and `apply`, but not for `update`; hence it seems values of type `IArray` cannot be updated.
 
 However, there is a potential hole due to pattern matching. Consider:
+
 ```scala
 val imm: IArray[Int] = ...
 imm match
   case a: Array[Int] => a(0) = 1
 ```
+
 The test will succeed at runtime since `IArray`s _are_ represented as
 `Array`s at runtime. But if we allowed it, it would break the fundamental abstraction of immutable arrays.
 
 __Aside:__ One could also achieve the same by casting:
+
 ```scala
 imm.asInstanceOf[Array[Int]](0) = 1
 ```
+
 But that is not as much of a problem since in Scala `asInstanceOf` is understood to be low-level and unsafe. By contrast, a pattern match that compiles without warning or error should not break abstractions.
 
 Note also that the problem is not tied to opaque types as match selectors. The following slight variant with a value of parametric
@@ -37,13 +43,15 @@ def f[T](x: T) = x match
   case a: Array[Int] => a(0) = 0
 f(imm)
 ```
+
 Finally, note that the problem is not linked to just opaque types. No unbounded type parameter or abstract type should be decomposable with a pattern match.
 
 ### The Solution
 
 There is a new type `scala.Matchable` that controls pattern matching. When typing a pattern match of a constructor pattern `C(...)` or
 a type pattern `_: C` it is required that the selector type conforms
 to `Matchable`. If that's not the case a warning is issued. For instance when compiling the example at the start of this section we get:
+
 ```
 > sc ../new/test.scala -source 3.1
 -- Warning: ../new/test.scala:4:12 ---------------------------------------------
@@ -52,18 +60,20 @@ to `Matchable`. If that's not the case a warning is issued. For instance when co
   |            pattern selector should be an instance of Matchable,
   |            but it has unmatchable type IArray[Int] instead
 ```
+
 To allow migration from Scala 2 and cross-compiling
 between Scala 2 and 3 the warning is turned on only for `-source 3.1-migration` or higher.
 
 `Matchable` is a universal trait with `Any` as its parent class. It is
 extended by both `AnyVal` and `AnyRef`. Since `Matchable` is a supertype of every concrete value or reference class it means that instances of such classes can be matched as before. However, match selectors of the following types will produce a warning:
 
- - Type `Any`: if pattern matching is required one should use `Matchable` instead.
- - Unbounded type parameters and abstract types: If pattern matching is required they should have an upper bound `Matchable`.
- - Type parameters and abstract types that are only bounded by some
-   universal trait: Again, `Matchable` should be added as a bound.
+- Type `Any`: if pattern matching is required one should use `Matchable` instead.
+- Unbounded type parameters and abstract types: If pattern matching is required they should have an upper bound `Matchable`.
+- Type parameters and abstract types that are only bounded by some
+  universal trait: Again, `Matchable` should be added as a bound.
 
 Here is the hierarchy of toplevel classes and traits with their defined methods:
+
 ```scala
 abstract class Any:
   def getClass
@@ -84,4 +94,3 @@ class Object extends Any, Matchable
 
 `Matchable` is currently a marker trait without any methods. Over time
 we might migrate methods `getClass` and `isInstanceOf` to it, since these are closely related to pattern-matching.
-