diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/product_editor/overview.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/editors/product_editor/overview.htm
index 324a366..405b81b 100644
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/editors/product_editor/overview.htm
+++ b/bundles/org.eclipse.pde.doc.user/guide/tools/editors/product_editor/overview.htm
@@ -2,7 +2,7 @@
 "http://www.w3.org/TR/html4/loose.dtd">
 <html lang="en">
 <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
+<meta name="copyright" content="Copyright (c) 2006, 2015 IBM Corporation and others. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
 <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
 <title>Product Overview</title>
 <link href="../../../book.css" rel="stylesheet" type="text/css">
@@ -31,9 +31,9 @@
 <h2>Exporting</h2>
 <p>To export an Eclipse product, you can invoke the <a href="../../export_wizards/export_product.htm">Eclipse Product Export</a> wizard via the hot link in the <strong>Exporting</strong> section. </p>
 <p><img src="../../../images/product_editor/overview_exporting.png" alt="Product Exporting" ></p>
-<p>To export a single product configuration to multiple platforms, you need to have the RCP delta pack installed. It is available for download from the same place as the Eclipse SDK. The RCP delta pack contains all the different platform-specific fragments needed for all supported platforms. </p>
-<p>Once the RCP delta pack is in the target platform, PDE detects the presence of the <em>org.eclipse.equinox.launchers</em> feature and enables the cross-platform export mode.</p>
-<p>Note, to use the RCP delta pack, you have to ensure that the 'Build target platform based on the target's installed plug-ins' option remains unchecked in the <strong>Target Platform</strong> preference page.</p>
+<p>To export a single product configuration to multiple platforms, you need to have the org.eclipse.equinox.executable feature installed in the target platform. It is available from the Eclipse project's p2 repository. The org.eclipse.equinox.executable feature contains all the different platform-specific fragments needed for all supported platforms. </p>
+<p>Once the org.eclipse.equinox.executable feature is in the target platform, PDE detects the presence of the <em>org.eclipse.equinox.launchers</em> feature and enables the cross-platform export mode.</p>
+<p>Note, to use the org.eclipse.equinox.executable feature, you have to ensure that the 'Build target platform based on the target's installed plug-ins' option remains unchecked in the <strong>Target Platform</strong> preference page.</p>
 
 
 </body>
diff --git a/bundles/org.eclipse.pde.doc.user/guide/tools/export_wizards/export_product.htm b/bundles/org.eclipse.pde.doc.user/guide/tools/export_wizards/export_product.htm
index 372d005..42e7507 100644
--- a/bundles/org.eclipse.pde.doc.user/guide/tools/export_wizards/export_product.htm
+++ b/bundles/org.eclipse.pde.doc.user/guide/tools/export_wizards/export_product.htm
@@ -2,7 +2,7 @@
 "http://www.w3.org/TR/html4/loose.dtd">
 <html lang="en">
 <head>
-<meta name="copyright" content="Copyright (c) IBM Corporation and others 2006, 2011. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
+<meta name="copyright" content="Copyright (c) 2006, 2015 IBM Corporation and others. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." >
 <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
 <title>Product Export</title>
 <script language="JavaScript" type="text/javascript" src="PLUGINS_ROOT/org.eclipse.help/livehelp.js"></script>
@@ -37,7 +37,7 @@
 <p>The <strong>Generate metadata repository</strong> option allows you to also generate p2 metadata along with your exported feature.  This does not create a p2-enabled product, just the metadata which can then be used to install using p2.</p>
 
 <h2>One-Click Cross-Platform Export</h2>
-<p>The <strong>Export for multiple platforms</strong> option is only available when PDE detects that the RCP delta pack is installed in the target platform. When this option is selected, a second wizard page is available and displays a list of available platforms to export to. This list is compiled by navigating the directory structure of the installed <em>org.eclipse.platform.launchers</em> feature to retrieve the different platform combinations. </p>
+<p>The <strong>Export for multiple platforms</strong> option is only available when PDE detects that the org.eclipse.equinox.executable feature is installed in the target platform. When this option is selected, a second wizard page is available and displays a list of available platforms to export to. This list is compiled by navigating the directory structure of the installed <em>org.eclipse.platform.launchers</em> feature to retrieve the different platform combinations. </p>
 <p><img src="../../images/export_wizards/cross_platform.PNG" alt="Cross Platform Export" > </p>
 <p>In a single operation, PDE generates a product for each selected platform and places it in a directory whose name is of the form <em>&lt;os&gt;_&lt;ws&gt;_&lt;arch&gt;</em>.  The <em>os</em> variable represents the selected operating system.  The <em>ws</em> variable represents the selected windowing system.  And, the <em>arch</em> variable represents the selected processor architecture.</p>
 
diff --git a/bundles/org.eclipse.pde.doc.user/tasks/pde_p2_configuringproducts.htm b/bundles/org.eclipse.pde.doc.user/tasks/pde_p2_configuringproducts.htm
index 6de7234..fd69c82 100644
--- a/bundles/org.eclipse.pde.doc.user/tasks/pde_p2_configuringproducts.htm
+++ b/bundles/org.eclipse.pde.doc.user/tasks/pde_p2_configuringproducts.htm
@@ -2,7 +2,7 @@
 <html lang="en">
 <head>
   <meta name="copyright"
- content="Copyright (c) IBM Corporation and others 2009. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
+ content="Copyright (c) 2009, 2015 IBM Corporation and others. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
   <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
   <meta http-equiv="Content-Style-Type" content="text/css">
   <link rel="STYLESHEET" href="../book.css" charset="ISO-8859-1" type="text/css">
@@ -52,7 +52,7 @@
 	...
 </pre>
 <h3>Launchers</h3>
-<p>PDE/Build will automatically <a href="pde_p2_buildtasks.htm#brand_p2_artifacts">brand launchers</a> (which it gets from the org.eclipse.equinox.executable feature in the delta pack).  These launchers will be automatically included in the
+<p>PDE/Build will automatically <a href="pde_p2_buildtasks.htm#brand_p2_artifacts">brand launchers</a> (which it gets from the org.eclipse.equinox.executable feature).  These launchers will be automatically included in the
 product along with generated metadata that will set the appropriate <a href="../../org.eclipse.platform.doc.isv/reference/misc/runtime-options.html"><i>-startup</i> and <i>--launcher.library</i></a> arguments in the product ini file.</p>
 <p>Because of changes to the structure of <a href="pde_p2_featuremetadata.htm">feature metadata</a> with respect to root files, the org.eclipse.equinox.executable feature should not be included directly in your product.</p> 
 </body>
diff --git a/bundles/org.eclipse.pde.doc.user/tasks/pde_product_build.htm b/bundles/org.eclipse.pde.doc.user/tasks/pde_product_build.htm
index 2621d46..cc92cc2 100644
--- a/bundles/org.eclipse.pde.doc.user/tasks/pde_product_build.htm
+++ b/bundles/org.eclipse.pde.doc.user/tasks/pde_product_build.htm
@@ -2,7 +2,7 @@
 <html lang="en">
 <head>
   <meta name="copyright"
- content="Copyright (c) IBM Corporation and others 2006, 2011. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
+ content="Copyright (c) 2006, 2015 IBM Corporation and others. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page.">
   <meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
   <meta http-equiv="Content-Style-Type" content="text/css">
   <link rel="STYLESHEET" href="../guide/book.css" type="text/css">
@@ -46,8 +46,8 @@
 location of an eclipse install containing all the pre-built features
 and plug-ins
 that your product requires in features/ and plugins/
-subdirectories.&nbsp; The RCP delta pack (it is available
-from the eclipse download page) is mandatory as it includes the
+subdirectories.&nbsp; The org.eclipse.equinox.executable feature (it is available
+from the eclipse p2 repository) is mandatory as it includes the
 org.eclipse.platform.launchers feature which
 contains the launchers and root files necessary for a product.</li>
   <li><span style="font-weight: bold;">buildDirectory</span>:&nbsp; the