summaryrefslogtreecommitdiffstats
path: root/eng/test-plan.rst
diff options
context:
space:
mode:
authorJoel Sherrill <joel@rtems.org>2018-12-20 09:17:09 -0600
committerJoel Sherrill <joel@rtems.org>2018-12-20 09:17:09 -0600
commit6682434bf21f53d3bd64e0509b4df9524b17646a (patch)
tree47fb077ec49ffb58ad5187eb11175e6bff97adf2 /eng/test-plan.rst
parenteng: Unicode char (U+200B) (diff)
downloadrtems-docs-6682434bf21f53d3bd64e0509b4df9524b17646a.tar.bz2
Eliminate UTF-8 characters except superscripted 2 in i2c
Diffstat (limited to 'eng/test-plan.rst')
-rw-r--r--eng/test-plan.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/eng/test-plan.rst b/eng/test-plan.rst
index c85efd2..c992150 100644
--- a/eng/test-plan.rst
+++ b/eng/test-plan.rst
@@ -21,7 +21,7 @@ capabilities are part of the RTEMS Tester toolset.
Assuming that a requirements focused test suite is added to the open
RTEMS, tools will be needed to assist in verifying that requirements are
-“fully tested.” A fully tested requirement is one which is implemented
+"fully tested." A fully tested requirement is one which is implemented
and tested with associated logical tracing. Tools automating this analysis
and generating reporting and alerts will be a critical part of ensuring
the master technical data does not bit rot.