diff options
| author | Sebastian Huber <sebastian.huber@embedded-brains.de> | 2020-02-11 07:32:17 +0100 |
|---|---|---|
| committer | Sebastian Huber <sebastian.huber@embedded-brains.de> | 2020-02-11 07:33:38 +0100 |
| commit | c95724b793297994685804fcdaeb324a23cf1fd7 (patch) | |
| tree | 463f3fa726b0cb2323f99d95ee8d290b07e5e300 | |
| parent | c-user: Clarify CONFIGURE_DIRTY_MEMORY (diff) | |
| download | rtems-docs-c95724b793297994685804fcdaeb324a23cf1fd7.tar.bz2 | |
c-user: Use contents instead of content
The memory values are countable.
Update #3843.
| -rw-r--r-- | c-user/configuring_a_system.rst | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/c-user/configuring_a_system.rst b/c-user/configuring_a_system.rst index a013d45..bc2b37a 100644 --- a/c-user/configuring_a_system.rst +++ b/c-user/configuring_a_system.rst @@ -453,7 +453,7 @@ DESCRIPTION: NOTES: Dirtying memory can add significantly to system boot time. It may assist in - finding code that incorrectly assumes the content of free memory areas is + finding code that incorrectly assumes the contents of free memory areas is cleared to zero during system initialization. In case :ref:`CONFIGURE_ZERO_WORKSPACE_AUTOMATICALLY` is also defined, then the memory is first dirtied and then zeroed. |