summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorMarçal Comajoan Cara <mcomajoancara@gmail.com>2018-11-07 18:57:47 +0100
committerSebastian Huber <sebastian.huber@embedded-brains.de>2018-11-09 14:59:59 +0100
commit495a84c804503b1e77dd2542bf3dee95f25e7237 (patch)
treeff812ab433b307500b558790761a290e451c9310
parent3c6df360880b9161ab1706534e3d49ea39b750b1 (diff)
downloadrtems-docs-495a84c804503b1e77dd2542bf3dee95f25e7237.tar.bz2
user: spelling and grammar fixes
This work was part of GCI 2018.
-rw-r--r--user/ecosys/index.rst6
-rw-r--r--user/overview/index.rst4
2 files changed, 5 insertions, 5 deletions
diff --git a/user/ecosys/index.rst b/user/ecosys/index.rst
index f41cbb3..d32c6d0 100644
--- a/user/ecosys/index.rst
+++ b/user/ecosys/index.rst
@@ -12,10 +12,10 @@ Ecosystem
The RTEMS Ecosystem is the collection of tools, packages, code, documentation
and online content provided by the RTEMS Project. The ecosystem provides a way
to develop, maintain, and use RTEMS. It's parts interact with the user, the
-host environment, and each other to make RTEMS accessable, useable and
+host environment, and each other to make RTEMS accessible, useable and
predicable.
-The ecosystem is for users, developers and maintainers and it is an on going
+The ecosystem is for users, developers and maintainers and it is an ongoing
effort that needs your help and support. The RTEMS project is always improving
the way it delivers the kernel to you and your feedback is important so please
join the mailing lists and contribute back comments, success stories, bugs and
@@ -58,7 +58,7 @@ that can be used to audit the build process so their configuration can be
documented.
The ecosystem is based around the source code used in the various parts,
-compontents and items of the RTEMS development environment. A user can create
+components and items of the RTEMS development environment. A user can create
an archive of the complete build process including all the source code for long
term storage. This is important for projects with a long life cycle.
diff --git a/user/overview/index.rst b/user/overview/index.rst
index a2c25a3..76bac36 100644
--- a/user/overview/index.rst
+++ b/user/overview/index.rst
@@ -69,7 +69,7 @@ interdependent, asynchronous or cyclical event streams.
Deadlines can be further characterized as either hard or soft based upon the
value of the results when produced after the deadline has passed. A deadline
is hard if the results have no value after the deadline has passed, or a
-catastophic event results from their intended use if not completed on time. In
+catastrophic event results from their intended use if not completed on time. In
contrast, results produced after a soft deadline may still have some value.
Another distinguishing requirement of real-time application systems is the
@@ -126,4 +126,4 @@ processors. In addition, one need not develop, test, debug, and document
routines to manage memory, pass messages, or provide mutual exclusion. The
developer is then able to concentrate solely on the application. By using
standard software components, the time and cost required to develop
-sophisticated real-time applications is significantly reduced.
+sophisticated real-time applications are significantly reduced.