Clean up test which is now out-of-date

Author: mkromberg

docs/Discussion/TechDetails.md

@@ -41,8 +41,6 @@ Note that *unnamed* namespaces are **NOT** supported, either as endpoints of a L
 
 - Changes made using `←`, `⎕NS`, `⎕FX`, `⎕FIX`, `⎕CY`, `)NS` and `)COPY` are not currently detected. For Link to be aware of the change, a call must be made to [Link.Fix](../API/Link.Fix.md). Similarly, deletions with `⎕EX` or `)ERASE` must be replaced by a call to [Link.Expunge](../API/Link.Expunge.md).
 
-- In Dyalog versions 18.2 or earlier, changes made using the line or "del" editor are not detected.
-
 - The detection of external changes to files and directories is currently only supported if a supported flavour of .NET is available to the interpreter. Note that the built-in APL editor *will* detect changes to source files on all platforms, when it opens an editor window.
 
 - Source code must not have embedded newlines within character constants. Although `⎕FX` does allow this, Link will error if this is attempted. This restriction comes because newline characters would be interpreted as a new line when saved as text file. When newline characters are needed in source code, they should be implemented by a call to `⎕UCS` e.g. `newline←⎕UCS 13 10  ⍝ carriage-return + line-feed`
@@ -55,7 +53,7 @@ Note that *unnamed* namespaces are **NOT** supported, either as endpoints of a L
 
 ## How does Link work?
 
-Some people need to know what is happening under the covers before they can relax and move on. If you are not one of those people, do not waste any further time on this section. If you do read it, understand that things may change under the covers without notice, and we will not allow a requirement to keep this document up-to-date to delay work on the code. It is reasonably accurate as of February 2024, at the end of the Link 4.0 development cycle.
+Some people need to know what is happening under the covers before they can relax and move on. If you are not one of those people, do not waste any further time on this section. If you do read it, understand that things may change under the covers without notice, and we will not allow a requirement to keep this document up-to-date to delay work on the code. It is reasonably accurate as of March 2025, at the end of the Link 4.1 development cycle.
 
 **Terminology:** In the following, the term *object* is used very loosely to refer to functions, operators, namespaces, classes and arrays.
 
@@ -90,7 +88,7 @@ If .NET is available, Link uses a File System Watcher to monitor linked director
 
 ### The Source of Link itself
 
-Link consists of a set of API functions which are loaded into the namespace `⎕SE.Link`, when APL starts, from **$DYALOG/StartupSession/Link**. The user command file **$DYALOG/SALT/SPICE/Link.dyalog** provides access to the interactive user command covers that exist for most of the API functions. Link 4.0 is pre-installed with Dyalog version 19.0 or later. To use version 4.0 with Dyalog 18.2, see the [installation instructions](../Usage/Installation.md).
+Link consists of a set of API functions which are loaded into the namespace `⎕SE.Link`, when APL starts, from **$DYALOG/StartupSession/Link**. The user command file **$DYALOG/SALT/SPICE/Link.dyalog** provides access to the interactive user command covers that exist for most of the API functions. Link 4.1 is pre-installed with Dyalog version 20.0 or later. To use version 4.1 with Dyalog 19.0, see the [installation instructions](../Usage/Installation.md).
 
 ### The Crawler
 

docs/Usage/Arrays.md

@@ -1,6 +1,6 @@
 # Array Formats
 
-By default, Link uses *APL Array Notation (APLAN)* to store arrays in text files. While APLAN is a good format for describing numeric data, nested arrays and many high rank arrays, it is not ideal for storing text data. Link 4.0 introduces experimental support for storing multi-line character data in simple text files.
+By default, Link uses *APL Array Notation (APLAN)* to store arrays in text files. While APLAN is a good format for describing numeric data, nested arrays and many high rank arrays, it is not ideal for storing text data. Link 4.0 introduced experimental support for storing multi-line character data in simple text files.
 
 The configuration setting `text` can be used to enable this feature: If `text` is set to `'aplan'` (the default) then all arrays will be store using APLAN. If `text` is set to `'plain'` then text arrays that adhere to a set of very specific criteria will instead be stored in plain text files. You can set this option when a link is created, or using [`Link.Configure`](../API/Link.Configure.md).
 

docs/Usage/index.md

@@ -147,7 +147,7 @@ However, if you have arrays that represent error tables, range definitions or ot
 Added: #.stats.Directions
 ```
 
-By default, Link uses *APL Array Notation* to store arrays in text files. Link 4.0 introduces experimental support for storing multi-line character data in simple text files. For more information, see the section on [array formats](../Usage/Arrays.md).
+By default, Link uses *APL Array Notation* to store arrays in text files. Link 4.0 introduced experimental support for storing multi-line character data in simple text files. For more information, see the section on [array formats](../Usage/Arrays.md).
 
 Once you have created a source file for an array, Link *will* update that file if you use the editor to modify the array. Only if you modify the array using assignment or other means than the editor will you need to call [Link.Add](../API/Link.Add.md) to force an update of the source file.
 

docs/index.md

@@ -11,7 +11,7 @@
 ## Link is NOT...
 
 - **A source code management system**: Link itself has no source code management features. As mentioned above, you will need to use a separate tool like Git to manage the source files that Link will allow you to use and modify from Dyalog APL.
-- **A database management system:** although Link is able to store APL arrays using a pre-release of the *literal array notation*, this is only intended to be used for constants which you consider to be part of the source code of your applications. Although all functions and operators that you define using the editor will be written to source files by default, source files are only created for arrays by explicit calls to [Link.Add](API/Link.Add.md) or by specifying optional parameters to [Link.Export](API/Link.Export.md). Application data should be stored in a database management system or files managed by the application.
+- **A database management system:** although Link is able to store APL arrays using *array notation*, this is only intended to be used for constants which you consider to be part of the source code of your applications. Although all functions and operators that you define using the editor will be written to source files by default, source files are only created for arrays by explicit calls to [Link.Add](API/Link.Add.md) or by specifying optional parameters to [Link.Export](API/Link.Export.md). Application data should be stored in a database management system or files managed by the application.
 
 ## Link fundamentals
 
@@ -37,7 +37,9 @@ If .NET is available, then any changes made to the external files using a text e
 !!!Note
 	For Dyalog to automatically update workspace contents due to file changes requires .NET.
 
-	The .NET Framework is included with Microsoft windows. For other platforms, .NET can be downloaded from [dotnet.microsoft.com/download](https://dotnet.microsoft.com/download).
+	The .NET Framework is included with Microsoft windows. For other platforms
+     or more recent versions of .NET, .NET can be downloaded from
+     [dotnet.microsoft.com/download](https://dotnet.microsoft.com/download).
 
 	To find out which versions are supported, see [section 2.1 of the .NET Interface Guide](https://docs.dyalog.com/latest/dotNET%20Interface%20Guide.pdf) and under the heading "Prerequisites" in [chapter 1 of the Dyalog for Microsoft Windows .NET Framework Interface Guide](https://docs.dyalog.com/latest/Dyalog%20for%20Microsoft%20Windows%20.NET%20Framework%20Interface%20Guide.pdf).