More docs fixes

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

@@ -99,9 +99,9 @@ affect implicits on the language level.
     buzz(1)   // error: ambiguous
     ```
  7. The rule for picking a _most specific_ alternative among a set of overloaded or implicit
-    alternatives is refined to take inferable parameters into account. All else
-    being equal, an alternative that takes some implicit parameters is taken to be less specific
-    than an alternative that takes none. If both alternatives take implicit parameters, we try
+    alternatives is refined to take context parameters into account. All else
+    being equal, an alternative that takes some context parameters is taken to be less specific
+    than an alternative that takes none. If both alternatives take context parameters, we try
     to choose between them as if they were methods with regular parameters.
     The following paragraph in the SLS is affected by this change:
 

docs/docs/reference/contextual/relationship-implicits.md

@@ -50,7 +50,7 @@ final implicit def given_Context = ctx
 Anonymous given instances get compiler synthesized names, which are generated in a reproducible way from the implemented type(s). For example, if the names of the `IntOrd` and `ListOrd` givens above were left out, the following names would be synthesized instead:
 ```scala
 given given_Ord_Int as Ord[Int] { ... }
-given given_Ord_List[T] as Ord[List[T]] { ... }
+given given_Ord_List_T[T](using ord: Ord[T]) as Ord[List[T]] { ... }
 ```
 The synthesized type names are formed from