rtems/rtems-docs
1
0
Fork 0
mirror of https://git.rtems.org/rtems-docs/ synced 2025-05-15 01:37:16 +08:00
Code Issues Packages Projects Releases Wiki Activity

user: spelling and grammar fixes

Browse Source 
This work was part of GCI 2018.
This commit is contained in:
Marçal Comajoan Cara 2018-11-07 18:57:47 +01:00 committed by Sebastian Huber
parent 3c6df36088
commit 495a84c804
2 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
user/ecosys/index.rst
View File

@ -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.

4
user/overview/index.rst
View File

@ -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.