From b8fa9f8d250e540174a0aa318cab66e2f03ecb9e Mon Sep 17 00:00:00 2001
From: ArkadiuszMichalski <crimsteam@gmail.com>
Date: Wed, 24 Feb 2021 18:10:21 +0100
Subject: [PATCH] Due to the lack of BOOST hide info about SciLexer.dll

---
 Testing.md | 7 ++++---
 1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/Testing.md b/Testing.md
index 20496a4..16b9735 100644
--- a/Testing.md
+++ b/Testing.md
@@ -30,7 +30,7 @@ To make sure that the bug you are reporting has not been fixed in the current-bu
 2. Go to the [official current-build page](https://ci.appveyor.com/project/donho/notepad-plus-plus).
 3. Click on the `Job name` in the list for the `Unicode Debug` job compatible with your version of Notepad ++ (`platform = Win32` for 32-bit Notepad++ or  `platform = x64 for 64-bit Notepad++`).  Ignore completely the `mingw` build jobs, and the `Unicode Release` jobs.
 4. Click on the blue `Artifacts` link located in the upper right corner.
-5. Download the appropriate `.exe` file (depending on step 3, it will be either `Notepad++.Win32.Unicode Debug.exe` or `Notepad++.x64.Unicode Debug.exe`).  Note that although a `.dll` file is provided, it is typically not necessary to obtain this file ([check details](#using-a-different-version-of-scilexerdll-file)).
+5. Download the appropriate `.exe` file (depending on step 3, it will be either `Notepad++.Win32.Unicode Debug.exe` or `Notepad++.x64.Unicode Debug.exe`).  Note that although a `.dll` file is provided, it is typically not necessary to obtain this file<!-- ([check details](#using-a-different-version-of-scilexerdll-file))-->.
 6. Add this `.exe` file to your portable Notepad++ folder and start the program with this executable instead of the normal `notepad++.exe` that is present in this folder.
 7. Try to reproduce the problem in this current-build version.
 
@@ -44,10 +44,11 @@ To verify that a specific PR has fixed a bug or implemented a feature, please fo
 3. After getting to the page of the PR, click on the `Commits` tab visible on the PR page and you'll be taken to a different page.
 4. On this page, locate the bottom-most commit and locate a small green-colored checkmark -- it is actually a link -- to the right of the commit-time; click on it and a small box will open and a `Details` link will be visible; click on that to be taken to a different page.
 5. Proceed from the "Click on the job name in the list..." step in the instructions for ["Using the current build version of Notepad++"](#using-the-current-build-version-of-notepad) (above).
-
+<!--
 ## Using a different version of SciLexer.dll file ##
 
 Usually there is no need to change `SciLexer.dll` file to test out the [current-build](#using-the-current-build-version-of-notepad) or the [PR-build](#using-a-pull-request-pr-build-version-of-notepad) changes, because its code rarely changes from the last [released version](#using-the-latest-release-portable-version-of-notepad). It's only necessary when updating Scintilla or BOOST library to newer versions. If this happens, pay attention to: 
 - New `.dll` file can't be used with a "release" version of the `.exe` file (because the `.dll` is unsigned and the released `.exe` version expects to see a signed `.dll`). For this reason we recommend that you download the `Unicode Debug` version of `.exe` file in the above instructions.
 - When you download new `.dll` file (in the same way as `.exe` file described in the above instructions) you need to rename it to exactly `SciLexer.dll` and overwrite the previous file with it. Only one `SciLexer.dll` file can exist alongside the `.exe` file and that is the one that will be used. 
-- Instead of deleting/overwriting the previous `SciLexer.dll` file, you can also rename it, e.g. to `_SciLexer.dll`. In this way you can switch between different .`dll` versions. 
\ No newline at end of file
+- Instead of deleting/overwriting the previous `SciLexer.dll` file, you can also rename it, e.g. to `_SciLexer.dll`. In this way you can switch between different .`dll` versions. 
+-->
\ No newline at end of file