diff --git a/documentation/current/eiffelstudio/_images/Create_new_tests_2.png b/documentation/current/eiffelstudio/_images/Create_new_tests_2.png
new file mode 100644
index 00000000..2122892d
Binary files /dev/null and b/documentation/current/eiffelstudio/_images/Create_new_tests_2.png differ
diff --git a/documentation/current/eiffelstudio/_images/Create_new_tests_2.png.data b/documentation/current/eiffelstudio/_images/Create_new_tests_2.png.data
new file mode 100644
index 00000000..94a996b9
--- /dev/null
+++ b/documentation/current/eiffelstudio/_images/Create_new_tests_2.png.data
@@ -0,0 +1,3 @@
+title=Create new tests
+author=halw
+path=content/create-new-tests
diff --git a/documentation/current/eiffelstudio/eiffelstudio-guided-tour/recompiling-and-editing.wiki b/documentation/current/eiffelstudio/eiffelstudio-guided-tour/recompiling-and-editing.wiki
index 1be88736..c02711f3 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-guided-tour/recompiling-and-editing.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-guided-tour/recompiling-and-editing.wiki
@@ -17,7 +17,7 @@ Make sure that the Editing Tool is big enough to display the text of the class:
 
 The Editing Tool hosts a text editor which you can use to change the class text. Here the routine <code>display</code> starts by outputting a simple message; let's precede it by another line of display to check that we affected the outcome. We'll want to add the following two lines just after the <code>do</code>, before the first two instructions of the routine: 
 <code>
-            io.put_string ("This is some more added text") 
+            io.put_string ("THIS IS SOME ADDED TEXT") 
             io.new_line
 </code>
 
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/outputs-tool/external-compilation-pane.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/outputs-tool/external-compilation-pane.wiki
index 106d54fc..9e4b19b3 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/outputs-tool/external-compilation-pane.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/outputs-tool/external-compilation-pane.wiki
@@ -45,7 +45,7 @@ The figure below shows an example of picking the feature <code>make</code> and d
 
 ===View external code from the finalized folder===
 
-By default the code that you see in an external editor is from the workbench (W_code) folder. You can see the corresponding external code from the finalized (F_code) folder by holding the <code>CTRL</code> key while you drop the class or feature pebble.
+By default the code that you see in an external editor is from the workbench (W_code) folder. You can see the corresponding external code from the finalized (F_code) folder by holding the <code>CTRL</code> key while you drop the class or feature pebble. 
 
 
 
diff --git a/documentation/current/eiffelstudio/eiffelstudio-reference/outputs-tool/index.wiki b/documentation/current/eiffelstudio/eiffelstudio-reference/outputs-tool/index.wiki
index ac2124e7..5cbf5817 100644
--- a/documentation/current/eiffelstudio/eiffelstudio-reference/outputs-tool/index.wiki
+++ b/documentation/current/eiffelstudio/eiffelstudio-reference/outputs-tool/index.wiki
@@ -54,11 +54,11 @@ If you choose a value of '''False''', then the Outputs tool will remain visible
 
 The preference '''External compilation output prompted ''' (''C output panel prompted'', in earlier versions) controls whether the [[External compilation pane|External compilation pane]] appears whenever an external compilation (usually a C compilation) occurs. 
 
-The default value is '''False'''. In this case, the External compilation pane does not appear automatically when an external compilation occurs, except under the following conditions:
+The default value is '''False'''. In this case, the External compilation pane does not appear automatically when an external compilation occurs, except when both of the following conditions are ture:
 # The Outputs tool is already displayed, and
 # The Eiffel Compilation pane is active.
 
-When an external compilation is performed, and the Eiffel Compilation output pane is already active, the External Compilation pane will become the active pane. When the external compilation completes, under most circumstances the Eiffel Compilation pane will become active again. However, the Eiffel Compilation pane will not become active if there were external compilation errors, or if you activated some other output pane during the external compilation. 
+So, regardless of the preference value, when an external compilation is performed, and the Eiffel Compilation output pane is already active in the Outputs tool, the External Compilation pane will become the active pane. When the external compilation completes, under most circumstances the Eiffel Compilation pane will become active again. However, the Eiffel Compilation pane will not become active if there were external compilation errors, or if you activated some other output pane during the external compilation.