summaryrefslogtreecommitdiffstats
path: root/user/hardware/targets.rst
diff options
context:
space:
mode:
authorSebastian Huber <sebastian.huber@embedded-brains.de>2019-01-23 10:40:40 +0100
committerSebastian Huber <sebastian.huber@embedded-brains.de>2019-01-24 07:31:25 +0100
commit63735bc9d2ec845ebe070c9eb0bb45f60aefdebc (patch)
tree7d522088c8fe1c090bcc975536dc151a4a89e7c5 /user/hardware/targets.rst
parent5973f92f79137576cea870b8504d5cb5582c6ce8 (diff)
downloadrtems-docs-63735bc9d2ec845ebe070c9eb0bb45f60aefdebc.tar.bz2
user: Spell out third-party
Diffstat (limited to 'user/hardware/targets.rst')
-rw-r--r--user/hardware/targets.rst2
1 files changed, 1 insertions, 1 deletions
diff --git a/user/hardware/targets.rst b/user/hardware/targets.rst
index 4d5e87f..0357be7 100644
--- a/user/hardware/targets.rst
+++ b/user/hardware/targets.rst
@@ -12,7 +12,7 @@ Targets
*target* because RTEMS is specifically aimed at that target hardware. An RTEMS
executable is statically linked and executes in a single address space on the
target hardware. A statically linked executable means the RTEMS Kernel,
-drivers, third party packages and application code is linked into a single
+drivers, third-party packages and application code is linked into a single
executable image. A single address space means no virtual memory and no memory
protected process address space is running within the RTEMS arena and the RTEMS
executive, drivers and application have unprotected access to the whole address