Resolved ‘See the Reference docs’ lines that had nothing to link to

Author: alvinj

Diff for: _overviews/scala3-book/collections-classes.md

@@ -169,7 +169,11 @@ Similarly, when you use `:+` you know the list needs to be on the left:
 a :+ 4
 ```
 
-As explained in the Reference documentation, there are more technical ways to think about this, but this can be a helpful way to remember the method names.
+There are more technical ways to think about this, but this can be a helpful way to remember the method names.
+
+{% comment %}
+LATER: Add a discussion of `:` on method names, right-associativity, and infix operators.
+{% endcomment %}
 
 Also, a good thing about these symbolic method names is that they’re consistent.
 The same method names are used with other immutable sequences, such as `Seq` and `Vector`.
@@ -247,7 +251,7 @@ scala> x.take(1).foreach(println)
 1
 ````
 
-For more information on the uses, benefits, and drawbacks of strict and non-strict (lazy) collections, see the Reference documentation.
+For more information on the uses, benefits, and drawbacks of strict and non-strict (lazy) collections, see the “strict” and “non-strict” discussions on the [The Architecture of Scala 2.13’s Collections][strict] page.
 
 <!--
 Given that definition, collections can also be thought of in terms of being strict or lazy. In a _strict_ collection, memory for the elements is allocated immediately, and all of its elements are immediately evaluated when a transformer method is invoked. In a _lazy_ collection, memory for the elements is not allocated immediately, and transformer methods do not construct new elements until they are demanded.
@@ -389,8 +393,6 @@ a(2) = 50                             // ArrayBuffer(1, 2, 50, 4)
 a.update(0, 10)                       // ArrayBuffer(10, 2, 50, 4)
 ```
 
-See the Reference documentation for more `ArrayBuffer` information and examples.
-
 
 
 ## Maps
@@ -614,4 +616,4 @@ When you need more information about specialized collections, see the following
 
 
 
-
+[strict]: {% link _overviews/core/architecture-of-scala-213-collections.md %}

Diff for: _overviews/scala3-book/collections-methods.md

@@ -246,7 +246,7 @@ emptyList.headOption          // Option[Int] = None
 ```
 
 As shown, it doesn’t throw an exception, it simply returns the type `Option` that has the value `None`.
-You can learn more about this programming style in the Reference documentation.
+You can learn more about this programming style in the [Functional Programming][fp-intro] chapter.
 
 
 
@@ -408,8 +408,7 @@ res1: Int = 24
 
 ## Even more
 
-There are literally dozens of additional methods on the Scala collections types that will keep you from ever needing to write another `for` loop.
-See the Reference documentation for more details and examples.
+There are literally dozens of additional methods on the Scala collections types that will keep you from ever needing to write another `for` loop. See [Mutable and Immutable Collections][mut-immut-colls] and [The Architecture of Scala Collections][architecture] for many more details on the Scala collections.
 
 > As a final note, if you’re using Java code in a Scala project, you can convert Java collections to Scala collections.
 > By doing this you can use those collections in `for` expressions, and can also take advantage of Scala’s functional collections methods.
@@ -419,4 +418,7 @@ See the Reference documentation for more details and examples.
 
 [interacting]: {% link _overviews/scala3-book/interacting-with-java.md %}
 [lambdas]: {% link _overviews/scala3-book/fun-anonymous-functions.md %}
+[fp-intro]: {% link _overviews/scala3-book/fp-intro.md %}
+[mut-immut-colls]: {% link _overviews/collections-2.13/overview.md %}
+[architecture]: {% link _overviews/core/architecture-of-scala-213-collections.md %}
 

Diff for: _overviews/scala3-book/concurrency.md

@@ -174,9 +174,7 @@ Other transformation methods include:
 - `recover`
 - `recoverWith`
 
-
-See the `Future` class Scaladoc for a list of additional methods.
-Also, see the Concurrency section in the Reference documentation for more details on how futures work.
+See the [Futures and Promises][futures] page for a discussion of additional methods available to futures.
 
 
 
@@ -303,6 +301,9 @@ To summarize, a few key points about futures are:
 
 Also, as you saw with the `import` statements in these examples, the Scala `Future` depends on an `ExecutionContext`.
 
-For more details about futures, see [Futures and Promises](https://docs.scala-lang.org/overviews/core/futures.html), an article that discusses futures, promises, and execution contexts.
+For more details about futures, see [Futures and Promises][futures], an article that discusses futures, promises, and execution contexts.
 It also provides a discussion of how a `for` expression is translated into a `flatMap` operation.
 
+
+
+[futures]: {% link _overviews/core/futures.md %}

Diff for: _overviews/scala3-book/control-structures.md

@@ -8,10 +8,6 @@ next-page: domain-modeling-intro
 ---
 
 
-{% comment %}
-- TODO: Should this section show (a) general control structure syntax and (b) syntax rules, such as when `do` is required? I currently assumed this should be in the Reference.
-{% endcomment %}
-
 Scala has the control structures you expect to find in a programming language, including:
 
 - `if`/`then`/`else`
@@ -391,7 +387,6 @@ Otherwise, the catch-all case is represented by the `_` character, and `day` is
 
 > When writing simple `match` expressions like this, it’s recommended to use the `@switch` annotation on the variable `i`.
 > This annotation provides a compile time warning if the switch can’t be compiled to a `tableswitch` or `lookupswitch`, which are better for performance.
-> See the Reference documentation for more details.
 
 
 ### Using the default value
@@ -540,6 +535,12 @@ def pattern(x: Matchable): String = x match
   case _ => "Unknown"
 ```
 
+{% comment %}
+TODO: Add in the new Scala 3 syntax shown on this page:
+http://dotty.epfl.ch/docs/reference/changed-features/match-syntax.html
+{% endcomment %}
+
+
 
 ## try/catch/finally
 

Diff for: _overviews/scala3-book/fp-functional-error-handling.md

@@ -235,7 +235,7 @@ makeInt(x) match
 ```
 
 > There are several other ways to handle `Option` values.
-> See the Reference documentation for more details.
+> See the reference documentation for more details.
 {% endcomment %}
 
 
@@ -311,8 +311,6 @@ While this section focuses on the `Option` classes, Scala has a few other altern
 For example, a trio of classes known as `Try`/`Success`/`Failure` work in the same manner, but (a) you primarily use these classes when your code can throw exceptions, and (b) you want to use the `Failure` class because it gives you access to the exception message.
 For example, these `Try` classes are commonly used when writing methods that interact with files, databases, and internet services, as those functions can easily throw exceptions.
 
-You can learn more about the `Try` classes and the similar `Either`/`Right`/`Left` classes in the Reference documentation.
-
 
 
 ## A quick review

Diff for: _overviews/scala3-book/interacting-with-java.md

@@ -357,10 +357,3 @@ System.out.printf("x = %d\n", x);
 ```
 
 
-
-## More information
-
-This section highlights some of the main topics to know when integrating Scala and Java code bases.
-For more details, including a few other topics not covered here, see the _Interacting with Java_ section in the Reference documentation.
-
-

Diff for: _overviews/scala3-book/packaging-imports.md

@@ -391,10 +391,4 @@ As mentioned, one of the key design benefits of the “import given” syntax is
 
 
 
-## Summary
-
-While that covers almost all of the features of packing and imports, see the Reference documentation for a few more details and features.
-
-
-
 [contextual]: {% link _overviews/scala3-book/ca-contextual-abstractions-intro.md %}