Apply suggestions from code review

Co-Authored-By: Sébastien Doeraene <sjrdoeraene@gmail.com>

Author: julienrf

_sips/minutes/2019-06-08-sip-minutes.md

@@ -206,7 +206,7 @@ Martin: Hmm, we might not need inline on parameters
 
 [https://dotty.epfl.ch/docs/reference/metaprogramming/macros.html](https://dotty.epfl.ch/docs/reference/metaprogramming/macros.html)
 
-Presented by Oliver
+Presented by Olivier
 
 Miles: the example is too basic, no recursion: can we do typeclass derivation with this? (need recursion)
 
@@ -222,7 +222,7 @@ Adriaan/Seb: inline is simpler
 
 ### More general meta-programming talks
 
-Nicolas/Oliver present 3 "tiers" of meta-programming: inline, staging, dotty reflect
+Nicolas/Olivier present 3 "tiers" of meta-programming: inline, staging, dotty reflect
 
 At the end it becomes clear that these aren't desugarings from one to another (e.g. staging doesn't desugar
 to dotty reflect, it's its own thing, idem for inline to staging).
@@ -259,7 +259,7 @@ Martin: But we said we weren't adding anything to the standard library in 3.0
 
 Olivier: Are they necessary?
   * Yes's and No's
-  * Seb: in Scala.js I could use the
+  * Seb: in Scala.js I could use them
   * Seth: should we ask the community?
   * Miles: no, because you'll always find someone that says yes
 Decision: Find use cases and test performance
@@ -284,4 +284,3 @@ Without extending it has a subset of java.lang.Enum's API.
 You use `-Xsource V` and `-migration` to help get to version V
 Martin: I'd like a way to do it file-by-file
   * (Many): having different files use different versions of Scala sounds very confusing
-