diff --git a/Testing.md b/Testing.md
index 80af469..f63984f 100644
--- a/Testing.md
+++ b/Testing.md
@@ -23,24 +23,24 @@ Tip: you can run different versions of Notepad ++ at the same time with the `-mu
 notepad.exe -multiInst
 ```
 
-## Using the current build version of Notepad++ ##
+## Using the current-build version of Notepad++ ##
 
-To make sure that the bug you are reporting has not been fixed in the current build version please follow the steps below:
+To make sure that the bug you are reporting has not been fixed in the current-build version please follow the steps below:
 1. Download and extract the latest portable version as described in ["Using the latest-release portable version of Notepad++"](#using-the-latest-release-portable-version-of-notepad) (above).
-2. Go to the [official current build page](https://ci.appveyor.com/project/donho/notepad-plus-plus).
+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 `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.
-6. Add this `.exe` file to your portable Notepad++ folder and start 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.
+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.
+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.
 
-If the problem still exists in the current build version of Notepad++ then please report it. In the report you can add a note that you have performed the test procedure in accordance with the official guidelines. 
+If the problem still exists in the current-build version of Notepad++ then please report it. In the report you can add a note that you have performed the test procedure in accordance with the official guidelines. 
 
 ## Using a Pull-Request (PR) build version of Notepad++ ##
 
 To verify that a specific PR has fixed a bug or implemented a feature, please follow the steps below:
 1. Download and extract the latest portable version as described in ["Using the latest-release portable version of Notepad++"](#using-the-latest-release-portable-version-of-notepad) (above).
-2. Go to the page of the PR.  If you know the PR number (e.g. 9508) then the link is `https://github.com/notepad-plus-plus/notepad-plus-plus/pull/9508`.  The formula to find a link for any PR is to take the base link `https://github.com/notepad-plus-plus/notepad-plus-plus/pull/` and add the PR number to it after the final `/`.  If you don't know the PR number, but you know there is one, find the original issue and there should be a way to get to the PR from reading the issue comments.
+2. Go to the github web page of the PR.  If you know the PR number (e.g. 9508) then the link is `https://github.com/notepad-plus-plus/notepad-plus-plus/pull/9508`.  The formula to find a link for any PR is to take the base link `https://github.com/notepad-plus-plus/notepad-plus-plus/pull/` and add the PR number to it after the final `/`.  If you don't know the PR number, but you know there is one, locate the original issue web page and there should be a way to get to the PR from reading the issue comments.
 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).
\ No newline at end of file