commit 290b9b21571e6fcba6fc50da3772bc9e061d048c
author rbalduino <rbalduino> Wed Sep 26 20:31:32 2012 +0000
committer rbalduino <rbalduino> Wed Sep 26 20:31:32 2012 +0000
tree def1c8f7e928aa6de37c1e33ab703e55bdfb5f11
parent 52fd476a348508cbb9570a17457323acce645d3c

*** empty log message ***

epf_prac_151/core.tech.common.extend_supp/guidances/concepts/system_wide_requirements.xmi

diff --git a/epf_prac_151/core.tech.common.extend_supp/guidances/concepts/system_wide_requirements.xmi b/epf_prac_151/core.tech.common.extend_supp/guidances/concepts/system_wide_requirements.xmi
index ce3ef38..689d2b7 100644
--- a/epf_prac_151/core.tech.common.extend_supp/guidances/concepts/system_wide_requirements.xmi
+++ b/epf_prac_151/core.tech.common.extend_supp/guidances/concepts/system_wide_requirements.xmi
@@ -33,7 +33,7 @@
     Functional requirements
 </h4>
 <p>
-    Functional requirements include all the overarching, system-wide functional requirements that are not expressed as use
+    Functional requirements include all the over-arching, system-wide functional requirements that are not expressed as use
     cases. These functional requirements represent the main system features that are familiar within the business domain or
     technically oriented requirements such as auditing, licensing, localization, e-mail, online help, printing, reporting,
     security, system management, or workflow.


epf_prac_151/practice.bus.mdev.base/guidances/guidelines/customizing_method_content_elements.xmi

diff --git a/epf_prac_151/practice.bus.mdev.base/guidances/guidelines/customizing_method_content_elements.xmi b/epf_prac_151/practice.bus.mdev.base/guidances/guidelines/customizing_method_content_elements.xmi
index 27c4c98..c0bcdbe 100644
--- a/epf_prac_151/practice.bus.mdev.base/guidances/guidelines/customizing_method_content_elements.xmi
+++ b/epf_prac_151/practice.bus.mdev.base/guidances/guidelines/customizing_method_content_elements.xmi
@@ -95,7 +95,7 @@
 </p>
 <ul>
     <li>
-        If one does not already exist, create a plug-in to to contain the new role.
+        If one does not already exist, create a plug-in to contain the new role.
     </li>
     <li>
         In the new plug-in, create the new role and specify what work products the role should own.
@@ -115,7 +115,7 @@
 </p>
 <ul>
     <li>
-        If one does not already exist, create a plug-in to to contain the new task.
+        If one does not already exist, create a plug-in to contain the new task.
     </li>
     <li>
         In the new plug-in, create the new task, being sure to specify what role performs the task and what work
@@ -132,7 +132,7 @@
 </p>
 <ul>
     <li>
-        If one does not already exist, create a plug-in to to contain the new work product.
+        If one does not already exist, create a plug-in to contain the new work product.
     </li>
     <li>
         In the new plug-in, create the new work product. 
@@ -155,7 +155,7 @@
 </p>
 <ul>
     <li>
-        If one does not already exist, create a plug-in to to contain the method content element additions.
+        If one does not already exist, create a plug-in to contain the method content element additions.
     </li>
     <li>
         In the new plug-in, create an element of the same type as the element you want to add to an make that element
@@ -186,7 +186,7 @@
 </p>
 <ul>
     <li>
-        If one does not already exist, create a plug-in to to contain the method content element that will be replacing the
+        If one does not already exist, create a plug-in to contain the method content element that will be replacing the
         original.
     </li>
     <li>
@@ -220,7 +220,7 @@
 </p>
 <ul>
     <li>
-        If one does not already exist, create a plug-in to to contain the method content element with the new name.
+        If one does not already exist, create a plug-in to contain the method content element with the new name.
     </li>
     <li>
         In the new plug-in, create a method content element of the same type as the one you want to rename and give it the
@@ -244,7 +244,7 @@
 </p>
 <ul class="noindent">
     <li>
-        If one does not already exist, create a plug-in to to contain the customizations.
+        If one does not already exist, create a plug-in to contain the customizations.
     </li>
     <li>
         In the new plug-in, add a new role and make it a contributor to the role that you want to assign the work product
@@ -276,7 +276,7 @@
 </p>
 <ul>
     <li>
-        If one does not already exist, create a plug-in to to contain the customizations.
+        If one does not already exist, create a plug-in to contain the customizations.
     </li>
     <li>
         In the new plug-in, define a task that extends and replaces the original task.
@@ -300,7 +300,7 @@
 </p>
 <ul>
     <li>
-        If one does not already exist, create a plug-in to to contain the customizations.
+        If one does not already exist, create a plug-in to contain the customizations.
     </li>
     <li>
         In the new plug-in, define a task that extends and replaces the original task.


epf_prac_151/practice.tech.concurrent_testing.base/tasks/run_tests.xmi

diff --git a/epf_prac_151/practice.tech.concurrent_testing.base/tasks/run_tests.xmi b/epf_prac_151/practice.tech.concurrent_testing.base/tasks/run_tests.xmi
index b997bb6..67ac52f 100644
--- a/epf_prac_151/practice.tech.concurrent_testing.base/tasks/run_tests.xmi
+++ b/epf_prac_151/practice.tech.concurrent_testing.base/tasks/run_tests.xmi
@@ -48,7 +48,7 @@
   </sections>
   <sections xmi:id="_sQaC4DO2EduqsLmIADMQ9g" name="Analyze and communicate test results" guid="_sQaC4DO2EduqsLmIADMQ9g">
     <sectionDescription>&lt;p>&#xD;
-    Post the test results in a conspicuous place that is accessible to the entire team, such as a white board or wiki.&#xD;
+    Post the test results in a conspicuous place that is accessible to the entire team, such as a white board or Wiki.&#xD;
 &lt;/p>&#xD;
 &lt;p>&#xD;
     For each failing test script, analyze the Test Log to identify the cause of the test failure. Begin with failing tests&#xD;