[522407] Complete documentation for limitation

Bug: 522407
Change-Id: Ia6e29d11834cb8352cd9456b3ee8a125608bd1e6
Signed-off-by: Laurent Fasani <laurent.fasani@obeo.fr>

2 files changed, 6 insertions, 4 deletions

diff --git a/plugins/org.eclipse.sirius.doc/doc/specifier/general/Specifying_Viewpoints.html b/plugins/org.eclipse.sirius.doc/doc/specifier/general/Specifying_Viewpoints.html
index 06ea5cd4bd..56d15d0223 100644
--- a/plugins/org.eclipse.sirius.doc/doc/specifier/general/Specifying_Viewpoints.html
+++ b/plugins/org.eclipse.sirius.doc/doc/specifier/general/Specifying_Viewpoints.html
@@ -511,7 +511,7 @@
 		<h4 id="reloadVSM">Reload installed VSM</h4>
 		<p>Even though having your VSP in the runtime environment workspace is the best way to do dynamic development of your VSM, if your VSP is in the installed runtime plug-ins (that is the VSP plug-in is in the development environment workspace), you have the ability the reload it from your runtime to take external changes into account.
 			<br/>This is done with the 
-			<em>Reload installed VSM</em> action from the main eclipse tool bar. 
+			<em>Reload installed VSM</em> action from the main Eclipse tool bar. 
 			<br/>Click on 
 			<em>Reload installed VSM</em> will have automatically effects in opened representations(depending on refresh options).
 		</p>
@@ -521,7 +521,8 @@
 		<ul>
 			<li>The action is available only if specifier plug-ins are installed.</li>
 			<li>The action is available only if the Eclipse Runtime is a started from PDE (that is, is not a stand alone application).</li>
-			<li>Only the VSM is reloaded. The java classes that may have been changed in the VSP are updated as normal java classes managed in debug mode.</li>
+			<li>Only the VSM is reloaded. The Java classes that may have been changed in the VSP are updated as normal Java classes managed in debug mode.</li>
+			<li>If you delete the VSP in the host Eclipse, you may encounter unexpected exceptions.</li>
 		</ul>
 		<h3 id="migration">Migration from Previous Versions</h3>
 		<p>The 
diff --git a/plugins/org.eclipse.sirius.doc/doc/specifier/general/Specifying_Viewpoints.textile b/plugins/org.eclipse.sirius.doc/doc/specifier/general/Specifying_Viewpoints.textile
index 308a6e0ce6..920647b637 100644
--- a/plugins/org.eclipse.sirius.doc/doc/specifier/general/Specifying_Viewpoints.textile
+++ b/plugins/org.eclipse.sirius.doc/doc/specifier/general/Specifying_Viewpoints.textile
@@ -204,13 +204,14 @@ Note that Sirius does its best to take into account any change in the VSM, even
 h4(#reloadVSM). Reload installed VSM
 
 Even though having your VSP in the runtime environment workspace is the best way to do dynamic development of your VSM, if your VSP is in the installed runtime plug-ins (that is the VSP plug-in is in the development environment workspace), you have the ability the reload it from your runtime to take external changes into account.
-This is done with the _Reload installed VSM_ action from the main eclipse tool bar. 
+This is done with the _Reload installed VSM_ action from the main Eclipse tool bar. 
 Click on _Reload installed VSM_ will have automatically effects in opened representations(depending on refresh options).
 
 _Limitations_:
 * The action is available only if specifier plug-ins are installed.
 * The action is available only if the Eclipse Runtime is a started from PDE (that is, is not a stand alone application).
-* Only the VSM is reloaded. The java classes that may have been changed in the VSP are updated as normal java classes managed in debug mode.
+* Only the VSM is reloaded. The Java classes that may have been changed in the VSP are updated as normal Java classes managed in debug mode.
+* If you delete the VSP in the host Eclipse, you may encounter unexpected exceptions.
 
 h3(#migration). Migration from Previous Versions