Add blogpost for releases 3.0.1 and 3.0.2-RC1 - fix table of contents

Author: prolativ

blog/_posts/2021-07-21-scala-3.0.2RC1-is-here.md

@@ -13,7 +13,7 @@ Scala 3.0.2-RC1, in turn, incorporates new language improvements and bug fixes d
 
 You can expect the release of stable 3.0.2 and a release candidate for a the next version in 6 weeks from now (1st September).
 
-# Improved insertion of semicolons in logical conditions
+## Improved insertion of semicolons in logical conditions
 
 Scala 3's indentation based syntax is aimed at making your code more concise and readable. As it gets broader adoption, we consistently improve its specification to eliminate corner cases which might lead to ambiguities or counterintuitive behaviours.
 
@@ -32,7 +32,7 @@ if foo(bar)
 then //...
 ```
 
-If your intention is to have a block of code evaluating into a single condition you should add a new line and indentation directly after `if` , e.g.
+If your intention is to have a block of code evaluating into a single condition you should add a new line and indentation directly after `if`, e.g.
 
 ```scala
 if
@@ -49,7 +49,7 @@ if val cond = foo(bar)
 then //...
 ```
 
-# Towards better null safety in the type system
+## Towards better null safety in the type system
 
 The compiler option `-Yexplicit-nulls` modifies Scala's standard type hierarchy to allow easier tracing of nullable values by performing strict checks directly on the level of the type system rather than just relying on conventions (e.g. this prevents you from writing code like `val foo: Option[String] = Some(null)`, which would be otherwise valid Scala although very likely to cause a `NullPointerException` at some further point).
 
@@ -59,15 +59,15 @@ After the recently introduced changes with this option enabled the `Null` type b
 def foo[T <: Matchable](t: T) = t match { case null => () }
 ```
 
-# Method search by type signature
+## Method search by type signature
 
 You can now browse the documentation of Scala's API not only by names of methods but also by their type in a [Hoogle](https://hoogle.haskell.org)-like manner (but with Scala syntax) thanks to integration with [Inkuire](https://github.com/VirtusLab/Inkuire) brought up by [#12375](https://github.com/lampepfl/dotty/pull/12375).
 
 To find methods with the desired signature simply write in scaladoc's searchbar the type you would expect them to have after eta-expansion (as if they were functions rather than methods).
 
 ![image url "image Title"](https://user-images.githubusercontent.com/39772805/117478350-53f12a80-af5f-11eb-82ab-930ba565dacb.gif)
 
-# Typing escape hatch for structural types
+## Typing escape hatch for structural types
 
 Structural types may come in handy in many situations, e.g. when one wants to achieve a compromise between safety of static typing and ease of use when dealing with dynamically changing schemas of domain data structures. They have however some limitations. Among others structural typing doesn't normally play well with method overloading because some types of reflective dispatch algorithms (inlcuding JVM reflection) might not be able to choose the overloaded method alternative with the right signature without knowing upfront the exact types of the parameters after erasure. Consider the following snippet.
 
@@ -99,7 +99,7 @@ This snippet will compile as the compiler won't perform the precise signature ch
 
 [More details](https://dotty.epfl.ch/docs/reference/changed-features/structural-types-spec.html#limitations-of-structural-types)
 
-# Metaprogramming
+## Metaprogramming
 
 Keeping in mind how important metaprogramming has become to Scala developers (especially creators of libraries) we continue to make it more reliable by fixing reported bugs and more powerful by repealing formerly introduced limitations. If you're curious how it was done look at the PRs below:
 
@@ -109,7 +109,7 @@ Keeping in mind how important metaprogramming has become to Scala developers (es
 - Detect abstract inline method calls after inlining [#12777](https://github.com/lampepfl/dotty/pull/12777)
 - Fix implicit ValueOf synthesis [#12615](https://github.com/lampepfl/dotty/pull/12615)
 
-# Other notable improvements
+## Other notable improvements
 
 - Add Scala 3 batch commands for Windows [#13006](https://github.com/lampepfl/dotty/pull/13006)
 - Fix [#12981](https://github.com/lampepfl/dotty/issues/12981): show diagnostics levels (warn \| error) in REPL [#13000](https://github.com/lampepfl/dotty/pull/13000)
@@ -122,7 +122,7 @@ Keeping in mind how important metaprogramming has become to Scala developers (es
 - Preserve hard unions in more situations [#12654](https://github.com/lampepfl/dotty/pull/12654)
 - Better support type-heavy pattern matches [#12549](https://github.com/lampepfl/dotty/pull/12549)
 
-# Other notable bug fixes
+## Other notable bug fixes
 
 - Fix [#13046](https://github.com/lampepfl/dotty/issues/13046): override is a valid identifier in Java, not a keyword [#13048](https://github.com/lampepfl/dotty/pull/13048)
 - Don't emit Java generic signatures for constructors [#13047](https://github.com/lampepfl/dotty/pull/13047)
@@ -144,7 +144,7 @@ Keeping in mind how important metaprogramming has become to Scala developers (es
 - Always generate a partial function from a lambda [#12670](https://github.com/lampepfl/dotty/pull/12670)
 - Fix [#12572](https://github.com/lampepfl/dotty/issues/12572): Ignore default accessor bridges in non-native JS classes. [#12657](https://github.com/lampepfl/dotty/pull/12657)
 
-# Contributors
+## Contributors
 Thank you to all the contributors who made this release possible 🎉
 
 According to `git shortlog -sn --no-merges 3.0.1-RC2..3.0.2-RC1` these are: