[154456] adding files that build was not generating
diff --git a/docs/org.eclipse.wst.sse.doc.user/META-INF/MANIFEST.MF b/docs/org.eclipse.wst.sse.doc.user/META-INF/MANIFEST.MF
index 64df659..5721315 100644
--- a/docs/org.eclipse.wst.sse.doc.user/META-INF/MANIFEST.MF
+++ b/docs/org.eclipse.wst.sse.doc.user/META-INF/MANIFEST.MF
@@ -2,6 +2,6 @@
 Bundle-ManifestVersion: 2
 Bundle-Name: %Bundle-Name.0
 Bundle-SymbolicName: org.eclipse.wst.sse.doc.user; singleton:=true
-Bundle-Version: 1.0.201.qualifier
+Bundle-Version: 1.0.203.qualifier
 Bundle-Vendor: %Bundle-Vendor.0
 Bundle-Localization: plugin
diff --git a/docs/org.eclipse.wst.sse.doc.user/sse_toc.xml b/docs/org.eclipse.wst.sse.doc.user/sse_toc.xml
index c92d56e..36f3b7f 100644
--- a/docs/org.eclipse.wst.sse.doc.user/sse_toc.xml
+++ b/docs/org.eclipse.wst.sse.doc.user/sse_toc.xml
@@ -11,7 +11,9 @@
  *     IBM Corporation - initial API and implementation
  *******************************************************************************/ -->
 <toc label="Structured text editors" topics="topics/csrcedt004.html">
+   <topic label="Structured text editors" href="topics/csrcedt004.html">
       <topic label="Editing text coded in markup languages " href="topics/tsrcedt000.html">
+         <topic label="Source and batch validation" href="topics/cvalidate.html"/>
          <topic label="Setting preferences for structured text editors" href="topics/tsrcedt025.html">
             <topic label="Setting annotation preferences for markup languages" href="topics/tsrcedt001.html"/>
          </topic>
@@ -19,7 +21,10 @@
             <topic label="Content assist" href="topics/csrcedt006.html"/>
             <topic label="Making content assist work for JSP files" href="topics/tsrcedt023.html"/>
          </topic>
+         <topic label="Associating editors with file types" href="topics/tcontenttype.html"/>
+         <topic label="File Encoding" href="topics/cencoding.html"/>
          <topic label="Searching or finding text within a file" href="topics/tsrcedt007.html"/>
+         <topic label="Checking spelling" href="topics/tsrcedt010.html"/>
          <topic label="Adding and removing markup language templates - overview" href="topics/tsrcedt027.html">
             <topic label="Adding and removing HTML templates" href="topics/tsrcedt024.html"/>
             <topic label="Adding and removing JSP templates" href="topics/tsrcedt028.html"/>
@@ -33,4 +38,5 @@
             <topic label="Deleting or hiding snippet items or drawers" href="topics/tsrcedt016.html"/>
          </topic>
       </topic>
+   </topic>
 </toc>
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/cencoding.html b/docs/org.eclipse.wst.sse.doc.user/topics/cencoding.html
new file mode 100644
index 0000000..a63fabd
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.doc.user/topics/cencoding.html
@@ -0,0 +1,40 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+  PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2006 IBM Corporation and others.
+ * All rights reserved. This program and the accompanying materials
+ * are made available under the terms of the Eclipse Public License v1.0
+ * which accompanies this distribution, and is available at
+ * http://www.eclipse.org/legal/epl-v10.html
+ * 
+ * Contributors:
+ *     IBM Corporation - initial API and implementation
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>File Encoding</title>
+</head>
+<body id="cencoding"><a name="cencoding"><!-- --></a>
+<h1 class="topictitle1">File Encoding</h1>
+<div><p></p>
+<p> The character encoding in XML, (X)HTML files, and JSP files can be specified
+and invoked in many different ways; however, we recommend that you specify
+the encoding in each one of your source files, for that is where many XML,
+HTML, JSP editors expect to find the encoding.</p>
+<div class="p">For example, for JSP files, you might use the pageEncoding attribute and/or
+the contentType attribute in the page directive, as shown in the following
+example:<pre>&lt;%@ page language="java" contentType="text/html; charset=ISO-8859-1"
+    pageEncoding="ISO-8859-1"%&gt;</pre>
+</div>
+<div class="p">For XML files, you might use the encoding pseudo-attribute in the xml declaration
+at the start of a document or the text declaration at the start of an entity,
+as in the following example: <pre>&lt;?xml version="1.0" encoding="iso-8859-1" ?&gt;</pre>
+</div>
+<div class="p">For (X)HTML files, you might use the &lt;meta&gt; tag inside the &lt;head&gt;
+tags, as shown in the following example:<pre>&lt;meta http-equiv="Content-Type" content="text/html;charset=utf-8" /&gt;</pre>
+</div>
+</div>
+</body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/cvalidate.html b/docs/org.eclipse.wst.sse.doc.user/topics/cvalidate.html
new file mode 100644
index 0000000..05fe0f2
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.doc.user/topics/cvalidate.html
@@ -0,0 +1,54 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+  PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2006 IBM Corporation and others.
+ * All rights reserved. This program and the accompanying materials
+ * are made available under the terms of the Eclipse Public License v1.0
+ * which accompanies this distribution, and is available at
+ * http://www.eclipse.org/legal/epl-v10.html
+ * 
+ * Contributors:
+ *     IBM Corporation - initial API and implementation
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Source and batch validation</title>
+</head>
+<body id="csrcedt001"><a name="csrcedt001"><!-- --></a>
+<h1 class="topictitle1">Source and batch validation</h1>
+<div><p></p>
+<p>There are two types of validation that can occur when you are working with
+source files in a structured source editor: source validation and batch validation. </p>
+<div class="p">Source validation occurs as you type your code; this validation reflects
+the "unsaved" and "unbuilt" contents of the source you are editing. For example,
+if you were to type the following code in a JSP editor:<p><samp class="codeph">&lt;foo:bar&gt;</samp></p>
+where <samp class="codeph">foo:bar</samp>is
+a tag that does not exist, the problem would be discovered immediately and
+would appear underlined in the editor. The advantage of this type of validation
+is that it can alert you to errors instantly.<div class="note"><span class="notetitle">Note:</span> To turn source validation
+on (or off) for all structured text editors, click <span class="menucascade"><span class="uicontrol">Window</span> &gt; <span class="uicontrol">Preferences</span> &gt; <span class="uicontrol">General</span> &gt; <span class="uicontrol">Editors</span> &gt; <span class="uicontrol">Structured Text Editors</span></span> and check (or
+uncheck) <strong>Report problems as you type</strong>.</div>
+</div>
+<div class="p">Batch validation occurs on saved files. It can catch build process errors
+and other errors that the source validator cannot. For example, suppose you
+typed the following in a JSP editor:<p><samp class="codeph">&lt;%@ taglib uri="http://java.sun.com/jsf/html" prefix="h"%&gt;<br />
+&lt;%@ taglib uri="http://java.sun.com/jsf/html" prefix="h"%&gt;</samp></p>
+In
+this example, the same prefix is used twice. This would prompt the batch validator
+to trigger markers and to generate build warnings in the Problems view and
+in the Navigator. </div>
+<p>Batch validation can uncover errors in multiple files at once and give
+you a comprehensive view of where problematic code can be found in your project.
+Moreover, you do not need to open files in an editor to run batch validation.
+To run batch validation on specific files, select and right click the files
+in the Project Explorer and then select <span class="menucascade"><span class="uicontrol">Run Validation</span></span> from the popup menu.</p>
+<div class="note"><span class="notetitle">Note:</span> To set preferences for batch validation, click <span class="menucascade"><span class="uicontrol">Window</span> &gt; <span class="uicontrol">Preferences</span> &gt; <span class="uicontrol">Validation</span></span></div>
+</div>
+<div><div class="relconcepts"><strong>Related concepts</strong><br />
+<div><a href="csrcedt004.html" title="Structured text editor is any of several text editors that you can use to edit various markup languages such as HTML, JavaScript, or XML.">Structured text editors for markup
+languages</a></div>
+</div>
+</div></body>
+</html>
\ No newline at end of file
diff --git a/docs/org.eclipse.wst.sse.doc.user/topics/tcontenttype.html b/docs/org.eclipse.wst.sse.doc.user/topics/tcontenttype.html
new file mode 100644
index 0000000..ae9df23
--- /dev/null
+++ b/docs/org.eclipse.wst.sse.doc.user/topics/tcontenttype.html
@@ -0,0 +1,40 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE html
+  PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html lang="en-us" xml:lang="en-us">
+<head>
+<!-- /*******************************************************************************
+ * Copyright (c) 2000, 2006 IBM Corporation and others.
+ * All rights reserved. This program and the accompanying materials
+ * are made available under the terms of the Eclipse Public License v1.0
+ * which accompanies this distribution, and is available at
+ * http://www.eclipse.org/legal/epl-v10.html
+ * 
+ * Contributors:
+ *     IBM Corporation - initial API and implementation
+ *******************************************************************************/ -->
+<link rel="stylesheet" type="text/css" href="../../org.eclipse.wst.doc.user/common.css" />
+<title>Associating editors with additional files types</title>
+</head>
+<body id="tcontenttype"><a name="tcontenttype"><!-- --></a>
+<h1 class="topictitle1">Associating editors with additional files types</h1>
+<div><p></p>
+<div class="section"><p>You can associate certain editors with a file type by clicking
+on <span class="menucascade"><span class="uicontrol">Window</span> &gt; <span class="uicontrol">Preferences</span> &gt; <span class="uicontrol">General</span> &gt; <span class="uicontrol">Editors</span> &gt; <span class="uicontrol">File
+Association</span></span> and setting up the associations in the
+File Associations Window.</p>
+<p>Some Eclipse-based editors, however, will
+only recognize a file based on the contents of the file. Consequently, if
+you want to associate an additional file type with some editors, you may have
+to first map the content type with its file extension. To map a content type
+with a file extension, complete the following steps: </p>
+<ol><li>Click <span class="menucascade"><span class="uicontrol">Window</span> &gt; <span class="uicontrol">General</span> &gt; <span class="uicontrol">Content Types</span></span>. The Content Type window
+appears. </li>
+<li>Select a content type in the Content Type window, and then select <strong>Add</strong> .
+The Define a New File Type window appears.</li>
+<li>Type the name of the file type, and then click <strong>OK</strong>.</li>
+</ol>
+</div>
+</div>
+</body>
+</html>
\ No newline at end of file