Fixed text
diff --git a/epf_prac_151/practice.tech.abrd.base/tasks/get_rule_set_reports.xmi b/epf_prac_151/practice.tech.abrd.base/tasks/get_rule_set_reports.xmi
index 7208ea6..cbe368b 100644
--- a/epf_prac_151/practice.tech.abrd.base/tasks/get_rule_set_reports.xmi
+++ b/epf_prac_151/practice.tech.abrd.base/tasks/get_rule_set_reports.xmi
@@ -1,36 +1,36 @@
<?xml version="1.0" encoding="UTF-8"?>
-<org.eclipse.epf.uma:TaskDescription 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="-Zf7BWTSjLSrv650HXb5Bvw" name=",_LGd_MFtvEdykEsBjRsVfZw" guid="-Zf7BWTSjLSrv650HXb5Bvw" authors="Jerome Boyer" changeDate="2007-12-14T02:19:33.000-0800" version="7.5.1">
- <mainDescription><p>
- There are multiple type of reports the rule team can analyze:<a id="XE_rule_set__get_reports"
- name="XE_rule_set__get_reports"></a>
-</p>
-<ul>
- <li>
- The&nbsp;query report to list the rules part of the rule set, rule flow, package, activate or not.
- </li>
- <li>
- Static analysis of conflict resolution
- </li>
- <li>
- rules execution report
- </li>
-</ul>
-<p>
- S<a id="1028579" name="1028579">tatic rule analysis is a mechanism for checking whether the rules are semantically
- consistent. Inconsistencies can be found either in a single rule or in a set of rules</a>.
-</p>
-<p>
- For single rule the analysis will list the rule that never apply, when the conditions of the rule can never be met.
- This could happen when there is mis-used of and/or operator in combined conditions, or if the values in the conditions
- are not in the possible allowable values for a given attribute.<br />
-</p>
-<p>
- Evaluating rule inconsistency in a rule set leads to discover
-</p>
-<ul>
- <li>
- Equivalent rules&nbsp;rules with same conditions and&nbsp;actions.
- </li>
+<org.eclipse.epf.uma:TaskDescription 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="-Zf7BWTSjLSrv650HXb5Bvw" name=",_LGd_MFtvEdykEsBjRsVfZw" guid="-Zf7BWTSjLSrv650HXb5Bvw" authors="Jerome Boyer" changeDate="2011-09-02T08:37:47.489-0700" version="7.5.1">
+ <mainDescription><p>
+ There are multiple type of reports the rule team can analyze:<a id="XE_rule_set__get_reports"
+ name="XE_rule_set__get_reports"></a>
+</p>
+<ul>
+ <li>
+ The&nbsp;query report to list the rules part of the rule set, rule flow, package, activate or not.
+ </li>
+ <li>
+ Static analysis of conflict resolution
+ </li>
+ <li>
+ rules execution report
+ </li>
+</ul>
+<p>
+ S<a id="1028579" name="1028579">tatic rule analysis is a mechanism for checking whether the rules are semantically
+ consistent. Inconsistencies can be found either in a single rule or in a set of rules</a>.
+</p>
+<p>
+ For single rule the analysis will list the rule that never apply, when the conditions of the rule can never be met.
+ This could happen when there is mis-used of and/or operator in combined conditions, or if the values in the conditions
+ are not in the possible allowable values for a given attribute.<br />
+</p>
+<p>
+ Evaluating rule inconsistency in a rule set leads to discover
+</p>
+<ul>
+ <li>
+ Equivalent rules:&nbsp;rules with same conditions and&nbsp;actions.
+ </li>
</ul></mainDescription>
<purpose>Get different rule report to analyze the conformance to the expected results</purpose>
</org.eclipse.epf.uma:TaskDescription>