Small fixes in the FAQ markdown documents

Author: vogella

docs/FAQ/FAQ_How_do_I_create_an_executable_JAR_file_for_a_stand-alone_SWT_program.md

@@ -11,10 +11,10 @@ The detailed instructions for creating an executable JAR file for a stand-alone
 2.  Find the correct SWT JAR file for the desired target platform. You can download the desired ZIP file from [the SWT website](https://www.eclipse.org/swt/). For example, for Eclipse 3.3 and a target platform of Linux, download the file swt-3.3.1.1-gtk-linux-x86.zip. Expand this ZIP file and copy the swt.jar file to the runtime folder. Remember that this swt.jar file is specific to one platform, in this case Linux.
 3.  Create a manifest file for your application using the Eclipse text editor (e.g., myapplication-manifest.txt). The text of the manifest should be as follows:
 
-        > Manifest-Version: 1.0
-        > Class-Path: swt.jar 
-        > Main-Class: mypackage.MyClassWithMainMethod
-        > (blank line at end of file)
+                Manifest-Version: 1.0
+                Class-Path: swt.jar 
+                Main-Class: mypackage.MyClassWithMainMethod
+                (blank line at end of file)
 
 4.  Make sure the manifest file ends with a blank line. Put the name of your package and class that contains the main() method for the Main-Class.
 5.  In Eclipse, select File/Export/Java/Jar file and press Next.

docs/FAQ/FAQ_How_do_I_create_my_own_tasks,_problems,_bookmarks,_and_so_on.md

@@ -5,11 +5,11 @@ FAQ How do I create my own tasks, problems, bookmarks, and so on?
 
 Annotations can be added to resources in the workspace by creating IMarker objects. These markers are used to represent compile errors, to-do items, bookmarks, search results, and many other types of annotations. You can create your own marker types for storing annotations for use by your own plug-in. Each marker can store an arbitrary set of attributes. Attributes are keyed by a string, and the values can be strings, Booleans, or integers. The IMarker interface defines some common attribute types, but you are free to create your own attribute names for your markers. Here is an example snippet that creates a marker, adds some attributes, and then deletes it:
 
-      final IFile file = null;
-      IMarker marker = file.createMarker(IMarker.MARKER);
-      marker.setAttribute(IMarker.MESSAGE, "This is my marker");
-      marker.setAttribute("Age", 5);
-      marker.delete();
+            final IFile file = null;
+            IMarker marker = file.createMarker(IMarker.MARKER);
+            marker.setAttribute(IMarker.MESSAGE, "This is my marker");
+            marker.setAttribute("Age", 5);
+            marker.delete();
 
 When markers are created, modified, or deleted, a resource change event will be broadcast, telling interested parties about the change. You can search for markers by using the findMarkers methods on IResource.
 

docs/FAQ/FAQ_How_do_I_set_a_conditional_breakpoint.md

@@ -10,20 +10,18 @@ Conditions can also be expressed in terms of other breakpoint attributes, such a
 ### Why do I get the message "Conditional breakpoint has compilation error(s) - <variable> cannot be resolved" when my breakpoint gets hit?
 
 It can occur that an error message is issued when a conditional breakpoint gets hit, even though the breakpoint condition appears to be syntactically correct:
-
 
 
-[![Conditional Breakpoint Error.PNG](/images/f/f4/Conditional_Breakpoint_Error.PNG)](/File:Conditional_Breakpoint_Error.PNG)
+![Conditional breakpoint in java.lang.Class.PNG](https://github.com/eclipse-platform/eclipse.platform/blob/master/docs/FAQ/images/Conditional_Breakpoint_Error.PNG)  
 
 
 
 This can happen if you are setting a breakpoint in a class whose class file does not contain a local variable table. For example, let's say you want to set a conditional breakpoint on `Class.forName(String)`. If you have a source attachment for `rt.jar` the content assist will allow you to refer to the argument by its variable name, `className`. However, at debug runtime, the variable name will only be known if the class file contains a local variable table. Depending on the options used at compilation time, this information may have been stripped from the class file.
 
 In the **Variables** view of the debugger, the argument will appear as `arg`_n_, and that placeholder name can actually also be used in the conditional expression for the breakpoint. So, instead of using the variable name `className` in your conditional expression, you simply use the placeholder `arg0`:
 
-  
+![Conditional breakpoint in java.lang.Class.PNG](https://github.com/eclipse-platform/eclipse.platform/blob/master/docs/FAQ/images/Conditional_breakpoint_in_java.lang.Class.PNG)  
 
-[![Conditional breakpoint in java.lang.Class.PNG](/images/a/ae/Conditional_breakpoint_in_java.lang.Class.PNG)](/File:Conditional_breakpoint_in_java.lang.Class.PNG)
 
 
 

docs/FAQ/FAQ_How_do_I_support_formatting_in_my_editor.md

@@ -10,7 +10,7 @@ The following snippet from the Java source configuration installs a master strat
       MultiPassContentFormatter formatter= 
          new MultiPassContentFormatter(
          getConfiguredDocumentPartitioning(viewer), 
-         IDocument.DEFAULT\_CONTENT\_TYPE);
+         IDocument.DEFAULT_CONTENT_TYPE);
       formatter.setMasterStrategy(
          new JavaFormattingStrategy());
       formatter.setSlaveStrategy(

docs/FAQ/FAQ_Why_should_I_use_the_new_progress_service.md

@@ -7,13 +7,13 @@ Eclipse 3.0 introduced a central new workbench _progress service_. This service
 
 The service is used much like the SWT BusyIndicator. Simply pass an IRunnableWithProgress instance to the busyCursorWhile method. The UI will prevent further user input and report progress feedback until the runnable completes. Note that the runnable executes in a non-UI thread, so you will have to use asyncExec or syncExec to execute any code within the runnable that requires access to UI widgets:
 
-   IWorkbench wb = PlatformUI.getWorkbench();
-   IProgressService ps = wb.getProgressService();
-   ps.busyCursorWhile(new IRunnableWithProgress() {
-      public void run(IProgressMonitor pm) {
-         ... do some long running task
-      }
-   });
+         IWorkbench wb = PlatformUI.getWorkbench();
+         IProgressService ps = wb.getProgressService();
+         ps.busyCursorWhile(new IRunnableWithProgress() {
+            public void run(IProgressMonitor pm) {
+               ... do some long running task
+            }
+         });
 
 This progress service was introduced to unify a number of progress-reporting mechanisms in Eclipse 2.1. JFace provides a Progress Monitor dialog, SWT provides a busy indicator, and the workbench provides a progress indicator on the status line. Each of these mechanisms has its own advantages and disadvantages. The busy cursor is the least obtrusive and works well for tasks that typically take a second or less. The Progress dialog provides much more information and allows the user to cancel but is visually distracting, especially on short tasks as it pops up over the user's work. The status line progress monitor is a bit less obtrusive but doesn't give an obvious indication that the UI is not accepting further input, and the space for presenting progress indication is very constrained. The new progress service tries to achieve a balance by automatically adapting between a busy cursor and a dialog, depending on the situation.