sergiotarxz/nuttx
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

Fix all occurrences of "the the" in documentation and comments

Browse Source
This commit is contained in:
Gregory Nutt 2013-08-27 09:40:19 -06:00
parent 066b940223
commit b6703a660c
7 changed files with 16 additions and 16 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
Documentation/NXGraphicsSubsystem.html
View File

@ -1709,7 +1709,7 @@ void nx_getrectangle(NXWINDOW hwnd, FAR const struct nxgl_rect_s *rect,
<dt><code>dest</code>
<dd>The location to copy the memory region
<dt><code>deststride</code>
<dd>The width, in bytes, the the dest memory
<dd>The width, in bytes, of the dest memory
</dl></ul>
</p>
<p>
@ -2335,7 +2335,7 @@ void nxtk_getwindow(NXTKWINDOW hfwnd, FAR const struct nxgl_rect_s *rect,
<dt><code>dest</code>
<dd>The location to copy the memory region
<dt><code>deststride</code>
<dd>The width, in bytes, the the dest memory
<dd>The width, in bytes, of the dest memory
</dl>
</p>
<p>
@ -2689,7 +2689,7 @@ int nxtk_gettoolbar(NXTKWINDOW hfwnd, FAR const struct nxgl_rect_s *rect,
<dt><code>dest</code>
<dd>TThe location to copy the memory region.
<dt><code>deststride</code>
<dd>The width, in bytes, the the dest memory.
<dd>The width, in bytes, of the dest memory.
</dl>
</p>
<p>
@ -3522,7 +3522,7 @@ enum nx_fontid_e
<li>
<p>
<b><code>nuttx/graphics/Makefile</code></b>.
This file needs logic to auto-generate a C source file from the header file that you generated with the the <i>bdf-converter</i> program.
This file needs logic to auto-generate a C source file from the header file that you generated with the <i>bdf-converter</i> program.
Notice <code>NXFONTS_FONTID=2</code>; this must be set to the same font ID value that you defined in the <code>include/nuttx/nx/nxfonts.h</code> file.
</p>
<ul><pre>

2
Documentation/NfsHowto.html
View File

@ -249,7 +249,7 @@ nfsmount &lt;server-address&gt; &lt;mount-point&gt; &lt;remote-path&gt;
</p>
<p>
<b>Example</b>.
Suppose the the NFS server has been configured to export the directory <code>/export/shared</code>.
Suppose that the NFS server has been configured to export the directory <code>/export/shared</code>.
The the following command would mount that file system (assuming that the target also has privileges to mount the file system).
</p>
<ul><pre>

2
Documentation/NuttShell.html
View File

@ -1043,7 +1043,7 @@ nsh> df
nsh>
</pre></ul>
<p>
If <code>CONFIG_NSH_CMDOPT_DF_H</code> is defined in the NuttX configuration, the the <code>df</code> will also support an option <code>-h</code> which may be used to show the the volume information in <i>human readable</i> format.
If <code>CONFIG_NSH_CMDOPT_DF_H</code> is defined in the NuttX configuration, then the <code>df</code> will also support an option <code>-h</code> which may be used to show the volume information in <i>human readable</i> format.
</p>
<table width ="100%">

8
Documentation/NuttX.html
View File

@ -2612,7 +2612,7 @@ nsh>
Configurations available include include a verified NuttShell (NSH) configuration
(see the <a href="http://www.nuttx.org/Documentation/NuttShell.html">NSH User Guide</a>).
The NSH configuration supports the Nucleus2G's microSD slot and additional configurations
are available to exercise the the USB serial and USB mass storage devices.
are available to exercise the USB serial and USB mass storage devices.
However, due to some technical reasons, neither the SPI nor the USB device drivers are fully verified.
(Although they have since been verfiied on other platforms; this needs to be revisited on the Nucleus2G).
</p>
@ -2660,7 +2660,7 @@ nsh>
for USB serial deive and USB storage devices examples, and for the USB host HID keyboard driver.
Support for the USB host mass storage device can optionally be configured for the NSH example.
A driver for the <i>Nokia 6100 LCD</i> and an NX graphics configuration for the Olimex LPC1766-STK have been added.
However, neither the LCD driver nor the NX configuration have been verified as of the the NuttX-5.17 release.
However, neither the LCD driver nor the NX configuration have been verified as of the NuttX-5.17 release.
</p>
</li>
<li>
@ -4219,7 +4219,7 @@ Other memory:
so that is it compatible with the SPI drivers of other MCUs
(2013-6-16).
* configs/sam3u-ek/src/up_touchscreen.c and configs/sam4l-xplained/src/sam_mmcsd.c:
Changed needed because of the above change the the SAM3/4 SPI
Changed needed because of the above change to the SAM3/4 SPI
interface (2013-6-16).
* drivers/input/ads7843e.c: Remove the wait for the touchscreen busy
bit. I don't see the busy bit changing on the SAM3U-EK board. But
@ -4448,7 +4448,7 @@ Other memory:
* The sama5d3x-ek/hello now runs correctly (2013-7-28).
* configs/sama5d3x-ek/ostest/: This configuration has been modified
to run out NOR flash. More work is still needed to reconfigure the
SMC so the the NOR flash can work with the high clock (2013-7-28).
SMC so that the NOR flash can work with the high clock (2013-7-28).
* arch/arm/src/sama5/sam_clockconfig.c/h and
configs/sama5d3x-ek/src/sam_norflash.c: Add a file structure that
will (eventually) support reconfiguration of NOR flash when NuttX

2
Documentation/NuttXDemandPaging.html
View File

@ -232,7 +232,7 @@
<li>
<b>Sanity checking</b>.
This function will ASSERT if the currently executing task is the page fill worker thread.
The page fill worker thread is how the the page fault is resolved and all logic associated with the page fill worker
The page fill worker thread is how the page fault is resolved and all logic associated with the page fill worker
must be &quot;<a href="#MemoryOrg">locked</a>&quot; and always present in memory.
</li>
<li>

8
Documentation/NuttxPortingGuide.html
View File

@ -3513,7 +3513,7 @@ extern void up_ledoff(int led);
<p>
Each USB host class driver includes an intialization entry point that is called from the
application at initialization time.
This driver calls <code>usbhost_registerclass()</code> during this initialization in order to makes itself available in the event the the device that it supports is connected.
This driver calls <code>usbhost_registerclass()</code> during this initialization in order to makes itself available in the event the device that it supports is connected.
</p>
<p>
<b>Examples</b>:
@ -3559,7 +3559,7 @@ extern void up_ledoff(int led);
<li>
<p>
<b><code>include/nuttx/usb/usbdev_trace.h</code></b>.
Declarations needed to work the the NuttX USB device driver trace capability.
Declarations needed to work with the NuttX USB device driver trace capability.
That USB trace capability is detailed in <a href="UsbTrace.html">separate document</a>.
</p>
</li>
@ -4197,13 +4197,13 @@ void pm_activity(int priority);
enum pm_state_e pm_checkstate(void);
</pre></ul>
<p><b>Description:</b>
This function is called from the MCU-specific IDLE loop to monitor the the power management conditions.
This function is called from the MCU-specific IDLE loop to monitor the power management conditions.
This function returns the &quot;recommended&quot; power management state based on the PM configuration and activity reported in the last sampling periods.
The power management state is not automatically changed, however.
The IDLE loop must call <code>pm_changestate()</code> in order to make the state change.
</p>
<p>
These two steps are separated because the plaform-specific IDLE loop may have additional situational information that is not available to the the PM sub-system.
These two steps are separated because the platform-specific IDLE loop may have additional situational information that is not available to the PM sub-system.
For example, the IDLE loop may know that the battery charge level is very low and may force lower power states even if there is activity.
</p>
<p>

2
Documentation/NuttxUserGuide.html
View File

@ -8462,7 +8462,7 @@ struct fat_format_s
<li>
<p>
The entire mapped portion of the file must be present in memory.
Since it is assumed the the MCU does not have an MMU, on-demanding
Since it is assumed that the MCU does not have an MMU, on-demanding
paging in of file blocks cannot be supported. Since the while mapped
portion of the file must be present in memory, there are limitations
in the size of files that may be memory mapped (especially on MCUs