Merge

5jt · Feb 24, 2018 · a381341 · a381341
1 parent 6dc366b
commit a381341
Show file tree

Hide file tree

Showing 5 changed files with 5 additions and 5 deletions.
diff --git a/manuscript/01 Introduction.md b/manuscript/01 Introduction.md
@@ -103,7 +103,7 @@ Kai Jaeger & Stephen Taylor
 
 [^apltree]: _APLTree_ is the name of an open-source library that offers robust, tested and well documented solutions to many everyday problems you  face when addressing the tasks discussed in this book.
 
-  It also offers some powerful tools that support the development proccess. We will use this library extensively and discuss it in detail. More at the source: <http://aplwiki.com/CategoryAplTree>.
+  We will use this library extensively and discuss it in detail. More at the source: <https://aplteam.github.io/apltree>. You can also search for "apltree" on [GitHub](https://github.com).
 
 
 [^classes]: These days seasoned programmers often have strong opinions about whether to use an object-oriented approach or a functional approach, or to mix them both. 

diff --git a/manuscript/02 Structure.md b/manuscript/02 Structure.md
@@ -166,7 +166,7 @@ Note that we have some functions that start with lowercase characters while othe
 
 To expand this program into distributable software we’re going to add features, many of them drawn from the APLTree library. To facilitate that we’ll first organise the existing code into script files, and write a _build script_ to assemble a workspace from them.  
 
-I> The APLTree library is an open-source project hosted in the APL wiki. It offers solutions for many every-day problems a Dyalog APL programmer might run into. In the Cookbook we will use many of its members. For details see <http://aplwiki.com/CategoryAplTree>.
+I> The APLTree library is an open-source project hosted on [GitHub](https://github.com). It offers solutions for many every-day problems a Dyalog APL programmer might run into. In the Cookbook we will use many of its members. For details see <https://aplteam.github.io/apltree>.
 
 Start at the root namespace (`#`). We’re going to be conservative about defining names in `#`. Why? Right now the program stands by itself and can do what it likes in the workspace. But in the future your program might become part of a larger APL system. In that case it will share `#` with other objects you don’t know anything about right now. 
 

diff --git a/manuscript/04 Logging what happens .md b/manuscript/04 Logging what happens .md
@@ -451,7 +451,7 @@ A>
 A> `MyLogger` is localized in the header of `TxtToCsv`, meaning that when `TxtToCsv` ends, this instance of the `Logger` class is destroyed and the destructor is invoked. Since the Tracer was up and running, the destructor makes an appearance in the Tracer.
 
 
-[^apltree]: You can download all members of the APLTree library from the APL Wiki: <http://download.aplwiki.com/>
+[^apltree]: You can download all members of the APLTree library from the APL Wiki <http://download.aplwiki.com/> or from the project pages on [GitHub](https://github.com): search for "apltree" to get a full list. Note that all apltree projects are owned by "aplteam".
 
 [^bom]: Details regarding the BOM: <https://en.wikipedia.org/wiki/Byte_order_mark>
 

diff --git a/manuscript/05 Configuration settings.md b/manuscript/05 Configuration settings.md
@@ -396,7 +396,7 @@ And finally we create a new standalone EXE as before and run it to make sure tha
 [^semi]: So-called _semi-globals_ are variables to be read or set by functions to which they are not localised. They are _semi-globals_, rather than globals, because they are local to either a function or a namespace. From the point of view of the functions that do read or set them, they are indistinguishable from globals – they are just mysteriously ‘around’. 
 
 
-[^fire]: Fire stands for _Find and Replace_. It is a powerful tool for both search and replace operations in the workspace. It is also a member of the APLTree Open Source Library. For details see <http://aplwiki.com/Fire>. Fire is discussed in the chapter _Useful user commands_.
+[^fire]: Fire stands for _Find and Replace_. It is a powerful tool for both search and replace operations in the workspace. For details see <https://github.com/aplteam.Fire>. Fire is discussed in the chapter _Useful user commands_.
 
 
 *[HTML]: Hyper Text Mark-up language

diff --git a/manuscript/08 Testing — the sound of breaking glass.md b/manuscript/08 Testing — the sound of breaking glass.md
@@ -936,7 +936,7 @@ Pro
 Contra
 : We cannot know whether those test cases cover the same environment/s (different versions of Windows, different versions of Dyalog, domain-managed network or not, network drives or not, multi-threaded versus single-threaded, you name it) our application will run in. 
 
-That suggests we should incorporate the tests the modules come with into our own test suite. <!-- , although we are sure that not too many people/companies using modules from the APLTree library are actually doing this. --> 
+That suggests we should incorporate the tests the modules come with into our own test suite, although we are sure that not too many people/companies using modules from the APLTree library are actually doing this.
 
 It’s not difficult to do: every module has a workspace saved on GitHub that comes with everything needed to run the test cases.