APLTree project has moved to GitHub

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.
 
-  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).
+  We will use this library extensively and discuss it in detail. More at the source: <https://github.com/aplteam/apltree/wiki/Members>. 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. 

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 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>.
+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://github.com/aplteam/apltree/wiki>.
 
 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. 
 

manuscript/11-Providing-help.md

@@ -6,7 +6,7 @@
 
 Users expect applications to provide help in one way or another. One option is to provide the help as a hypertext system. Under Windows, CHM files are the standard way to provide such help. There are powerful applications available that can assist you in providing help; HelpAndManual [^ham] is just an example.
 
-However, we take a different approach here: rather than using any third-party software we use `Markdown2Help` from the APLTree library. That allows us to create a help system that:
+However, we take a different approach here: rather than using any third-party software we use `Markdown2Help` from the APL_cation [^aplcation] project. That allows us to create a help system that:
 
 * offers pretty much the same functionality as CHM.
 * allows us to keep the Help close to the code.
@@ -483,6 +483,8 @@ leanpub-end-insert
 
 [^ham]: <http://www.helpandmanual.com/>
 
+[^aplcation]: <https://github.com/aplteam/apltree/wiki/Members>
+
 
 *[HTML]: Hyper Text Mark-up language
 *[DYALOG]: File with the extension 'dyalog' holding APL code

manuscript/Appendix-04_Development-environment.md

@@ -161,7 +161,7 @@ Defining function keys is of course not exactly a challenge. Implementing it in
       ⎕SHADOW⊃list←'LL' 'DB' 'DI' 'ER' 'LC' 'DC' 'UC' 'RD' 'RL' 'RC' 'Rl' 'Ll' 'CP' 'PT' 'BH'
       ⍎¨{⍵,'←⊂''',⍵,''''}¨list
       r⍪←'F01'('')('(Reserved for help)')
-      r⍪←'F02'(')WSID',ER)(')wsid')
+      r⍪←'F02'(')WSID',ER)(')wsid')
       r⍪←'F03'('')('Show next hit')                  ⍝ Reserved for NX
       r⍪←'F04'('⎕SE.Display ')('Call "Display"')
       r⍪←'F05'(LL,'→⎕LC+1 ⍝ ',ER)('→⎕LC+1')