Fix typo identified by translators
diff --git a/epf_prac_151/practice.bus.mdev.base/guidances/guidelines/publishing.xmi b/epf_prac_151/practice.bus.mdev.base/guidances/guidelines/publishing.xmi
index 594a9d2..c398777 100644
--- a/epf_prac_151/practice.bus.mdev.base/guidances/guidelines/publishing.xmi
+++ b/epf_prac_151/practice.bus.mdev.base/guidances/guidelines/publishing.xmi
@@ -1,48 +1,48 @@
<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmi:id="-9lCfOj2da5Xm8VvefI9b5g" name="publishing,_Z7gHED08Ed-lU6YVR9_PJQ" guid="-9lCfOj2da5Xm8VvefI9b5g" changeDate="2010-05-17T10:01:26.000-0700" version="7.5.0">
- <mainDescription><p>
- Publishing an individual <a
- id="A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/concepts/practice_F5C8EAAB.html:.:.:"
- class="elementLink" href="./../../../core.default.uma_concept.base/guidances/concepts/practice_F5C8EAAB.html"
- guid="_qhCTAFRREd2CWscN8Mx6rg">Practice</a>&nbsp;is a valuable exercise as it allows you to see the practice in its
- published form, which may result in some refinements.&nbsp;
-</p>
-<p>
- Publishing an individual practice&nbsp;involves publishing a <a
- id="A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/method_configuration_C2B8FA8A.html:.:.:"
- class="elementLink"
- href="./../../../core.default.uma_concept.base/guidances/termdefinitions/method_configuration_C2B8FA8A.html"
- guid="__V7pAMaEEduMlb2cQZNTYw">method configuration</a>&nbsp;that specifies what practices will be published (the
- selected practice&nbsp;<a
- id="A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/method_plugin_190B9F5E.html:.:.:"
- class="elementLink"
- href="./../../../core.default.uma_concept.base/guidances/termdefinitions/method_plugin_190B9F5E.html"
- guid="_D4TLgMaGEduMlb2cQZNTYw">method plug-in</a>s and packages) and how they will appear in the published method (the
- navigation views).&nbsp;Such a configuration is usually not delivered to an end-user, but is quite helpful during the
- development of the practice.&nbsp;It is recommended that the name of the configuration include the name of the
- practice. For information on defining method configurations.&nbsp;
-</p>
-<p>
- For convenience publishing options may be stored in&nbsp;a configuration file.
-</p>
-<p>
- Once the configuration has been defined it can be published.&nbsp;&nbsp;
-</p>
-<h4>
- Publishing in the UMF
-</h4>
-<p>
- When defining configurations in the Unified Method Framework (UMF), you can use the generic navigation view defined in
- the default navigation view definition plug-in in the UMF core as the navigation view for the test configuration.
- Usually, that is all that is needed. However, feel free to define additional navigation views, if needed.&nbsp;For more
- information on how navigation views are implemented in the UMF, see Navigation Views in the UMF in&nbsp;<a
- class="elementLinkWithType"
- href="./../../../practice.bus.mdev.base/guidances/guidelines/defining_method_elements_CADE4FF6.html"
- guid="_fx7TMD3REd-realK_We5vA">Guideline: Defining Method Elements</a>.
-</p>
-<p>
- As with all configurations in the UMF, any configuration-specific elements (e.g., navigation views, welcome pages,
- processes, etc.) need to be define in a separate&nbsp;Publish plug-in for the test configuration and that Publish
- plug-in must be included in the test configuration.&nbsp;For more information on Publish plug-ins.
-</p><br /></mainDescription>
+<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-9lCfOj2da5Xm8VvefI9b5g" name="publishing,_Z7gHED08Ed-lU6YVR9_PJQ" guid="-9lCfOj2da5Xm8VvefI9b5g" changeDate="2011-10-10T10:23:30.727-0700" version="7.5.0">
+ <mainDescription><p>
+ Publishing an individual <a
+ id="A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/concepts/practice_F5C8EAAB.html:.:.:"
+ class="elementLink" href="./../../../core.default.uma_concept.base/guidances/concepts/practice_F5C8EAAB.html"
+ guid="_qhCTAFRREd2CWscN8Mx6rg">Practice</a>&nbsp;is a valuable exercise as it allows you to see the practice in its
+ published form, which may result in some refinements.&nbsp;
+</p>
+<p>
+ Publishing an individual practice&nbsp;involves publishing a <a
+ id="A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/method_configuration_C2B8FA8A.html:.:.:"
+ class="elementLink"
+ href="./../../../core.default.uma_concept.base/guidances/termdefinitions/method_configuration_C2B8FA8A.html"
+ guid="__V7pAMaEEduMlb2cQZNTYw">method configuration</a>&nbsp;that specifies what practices will be published (the
+ selected practice&nbsp;<a
+ id="A_-_-_C:/AMasell_cc_view/umf/lib751/shared/core.default.uma_concept.base/guidances/termdefinitions/method_plugin_190B9F5E.html:.:.:"
+ class="elementLink"
+ href="./../../../core.default.uma_concept.base/guidances/termdefinitions/method_plugin_190B9F5E.html"
+ guid="_D4TLgMaGEduMlb2cQZNTYw">method plug-in</a>s and packages) and how they will appear in the published method (the
+ navigation views).&nbsp;Such a configuration is usually not delivered to an end-user, but is quite helpful during the
+ development of the practice.&nbsp;It is recommended that the name of the configuration include the name of the
+ practice.
+</p>
+<p>
+ For convenience, publishing options may be stored in&nbsp;a configuration file.
+</p>
+<p>
+ Once the configuration has been defined it can be published.&nbsp;&nbsp;
+</p>
+<h4>
+ Publishing in the UMF
+</h4>
+<p>
+ When defining configurations in the Unified Method Framework (UMF), you can use the generic navigation view defined in
+ the default navigation view definition plug-in in the UMF core as the navigation view for the test configuration.
+ Usually, that is all that is needed. However, feel free to define additional navigation views, if needed.&nbsp;For more
+ information on how navigation views are implemented in the UMF, see Navigation Views in the UMF in&nbsp;<a
+ class="elementLinkWithType"
+ href="./../../../practice.bus.mdev.base/guidances/guidelines/defining_method_elements_CADE4FF6.html"
+ guid="_fx7TMD3REd-realK_We5vA">Guideline: Defining Method Elements</a>.
+</p>
+<p>
+ As with all configurations in the UMF, any configuration-specific elements (e.g., navigation views, welcome pages,
+ processes, etc.) need to be define in a separate&nbsp;Publish plug-in for the test configuration and that Publish
+ plug-in must be included in the test configuration.
+</p></mainDescription>
</org.eclipse.epf.uma:ContentDescription>
