michaelh/zephyr
1
0
Fork 0
Code Releases Activity

Change minor punctuation characters.

Browse source 
Corrected some punctuation characters to improve readability.

Change-Id: I44930a8a314f9fa5f3da216df3c7d2262c9cb1ef
Signed-off-by: Gerardo A. Aceves <gerardo.aceves@intel.com>
This commit is contained in:
Gerardo A. Aceves 2015-08-19 00:41:58 -05:00 • committed by Anas Nashif
commit a049bf3de8
4 changed files with 8 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

4
doc/kernel/microkernel/microkernel_memory_maps.rst
View file

@ -32,7 +32,7 @@ which can arise when using variable-size blocks.
Unlike a heap, more than one memory map can be defined, if needed. This
allows for a memory map with smaller blocks and others with larger-sized
blocks. (Alternatively, a memory pool object may be used.)
blocks. Alternatively, a memory pool object may be used.
Purpose
@ -56,7 +56,7 @@ The following parameters must be defined:
This specifies the number of memory blocks in the memory map.
*block_size*
This specifies the size (in bytes) of each memory block.
This specifies the size in bytes of each memory block.
Public Memory Map

2
doc/kernel/microkernel/microkernel_memory_pools.rst
View file

@ -17,7 +17,7 @@ to more closely match the actual needs of the requesting task.
Any number of memory pools can be defined in a microkernel system.
Each memory pool has a name that uniquely identifies it.
In addition, a memory pool defines minimum and maximum memory block sizes
(in bytes) and the number of maximum size blocks that the memory pool
in bytes and the number of maximum size blocks that the memory pool
contains.
A task that needs to use a memory block simply allocates it from a

4
doc/kernel/microkernel/microkernel_pipes.rst
View file

@ -34,7 +34,7 @@ the pipe must accept. The following pipe option values are supported:
Specifies that at least one data byte must be accepted by the pipe;
otherwise the send request fails.
:option:`_0_TO_N`
Specifies that any number of data bytes (including zero) may be accepted
Specifies that any number of data bytes, including zero, may be accepted
by the pipe; the send request never fails.
The pipe accepts data bytes from the sending task if they can be delivered
@ -171,7 +171,7 @@ The following parameters must be defined:
This specifies a unique name for the pipe.
*buffer_size*
This specifies the size (in bytes) of the pipe's ring buffer.
This specifies the size in bytes of the pipe's ring buffer.
If no ring buffer is to be used specify zero.

7
doc/kernel/networking/bluetooth.rst
View file

@ -46,10 +46,9 @@ Using Host System Bluetooth Controller in QEMU
==============================================
The host system's Bluetooth controller is connected to the second QEMU
serial line through a UNIX socket
(QEMU option :literal:`-serial unix:/tmp/bt-server-bredr`).
This option is already added to QEMU through :makevar:`QEMU_EXTRA_FLAGS`
in the Makefile.
serial line using a UNIX socket. This socket employs the QEMU option
:literal:`-serial unix:/tmp/bt-server-bredr`. This option is already
added to QEMU through :makevar:`QEMU_EXTRA_FLAGS` in the Makefile.
On the Host side, BlueZ allows to "connect" Bluetooth controller through
a so-called user channel.