Merge pull request scala#1124 from xingyif/futurelink

SethTisue · web-flow · commit ee96427a43d3 · 2018-08-06T14:00:44.000-07:00
Updated link to docs in core/
diff --git a/_overviews/core/actors.md b/_overviews/core/actors.md
@@ -460,7 +460,7 @@ is as follows:
 
 ### Starting remote actors
 
-A remote actor is uniquely identified by a [`Symbol`](http://www.scala-lang.org/api/2.9.1/scala/Symbol.html). This symbol is
+A remote actor is uniquely identified by a [`Symbol`](https://www.scala-lang.org/api/current/scala/Symbol.html). This symbol is
 unique to the JVM instance on which the remote actor is executed. A
 remote actor identified with name `'myActor` can be created as follows.
 
diff --git a/_overviews/core/futures.md b/_overviews/core/futures.md
@@ -15,7 +15,7 @@ permalink: /overviews/core/:title.html
 
 Futures provide a way to reason about performing many operations
 in parallel-- in an efficient and non-blocking way.
-A [`Future`](http://www.scala-lang.org/api/current/index.html#scala.concurrent.Future)
+A [`Future`](https://www.scala-lang.org/api/current/scala/concurrent/Future.html)
 is a placeholder object for a value that may not yet exist.
 Generally, the value of the Future is supplied concurrently and can subsequently be used.
 Composing concurrent tasks in this way tends to result in faster, asynchronous, non-blocking parallel code.
@@ -58,7 +58,7 @@ Both code snippets delegate the execution of `fatMatrix.inverse()` to an `Execut
 
 ## Execution Context
 
-Future and Promises revolve around [`ExecutionContext`s](http://www.scala-lang.org/api/current/index.html#scala.concurrent.ExecutionContext), responsible for executing computations.
+Future and Promises revolve around [`ExecutionContext`s](https://www.scala-lang.org/api/current/scala/concurrent/ExecutionContext.html), responsible for executing computations.
 
 An `ExecutionContext` is similar to an [Executor](http://docs.oracle.com/javase/7/docs/api/java/util/concurrent/Executor.html):
 it is free to execute  computations in a new thread, in a pooled thread or in the current thread
diff --git a/_overviews/core/string-interpolation.md b/_overviews/core/string-interpolation.md
@@ -97,7 +97,7 @@ In Scala, all processed string literals are simple code transformations.   Anyti
 
     id"string content"
 
-it transforms it into a method call (`id`) on an instance of [StringContext](http://www.scala-lang.org/api/current/index.html#scala.StringContext).
+it transforms it into a method call (`id`) on an instance of [StringContext](https://www.scala-lang.org/api/current/scala/StringContext.html).
 This method can also be available on implicit scope.   To define our own string interpolation, we simply need to create an implicit class that adds a new method
 to `StringContext`.  Here's an example:
 
