diff --git a/doc/org.eclipse.cdt.doc.user/tasks/cdt_o_tasksview.htm b/doc/org.eclipse.cdt.doc.user/tasks/cdt_o_tasksview.htm
index 7b56dded9e3..fc5b24f14c9 100644
--- a/doc/org.eclipse.cdt.doc.user/tasks/cdt_o_tasksview.htm
+++ b/doc/org.eclipse.cdt.doc.user/tasks/cdt_o_tasksview.htm
@@ -4,15 +4,29 @@
-Viewing and managing compile errors
+Dealing with compilation and other build errors
-
Viewing and managing compile errors
+
Dealing with compilation and other build errors
-
The following topics describe how to view and manage compile errors. The CDT displays compile errors in the Console view.
+
After a build finishes, CDT displays the build output in the Console View. The build output shows
+the result of build and a user can inspect it to find out if it was successful or not. To assist with that
+CDT Error Parsers scan build output and create Problem Markers which are presented in a variety of ways:
+
+
as highlighted lines on the console,
+
in the Problems View,
+
as icon decorators in the Project Explorer on the file, its parent folders and the project,
+
icons in editor's overview rulers,
+
as squiggly line marking the problematic code in editor.
+
+There are 3 types of Problem Markers: Errors, Warnings and Info. A user can control how the markers are
+generated on "Error Parsers" Preference page.
+
+
+
The following topics describe how to view and manage compile errors.
Jumping to errors