diff --git a/Documentation/NXGraphicsSubsystem.html b/Documentation/NXGraphicsSubsystem.html index 48e4e376e45..4f7833acdb2 100644 --- a/Documentation/NXGraphicsSubsystem.html +++ b/Documentation/NXGraphicsSubsystem.html @@ -356,7 +356,7 @@

1NXMU and NXSU are interchangeable other than (1) certain start-up - and intialization APIs (as described below), and (2) timing. With NXSU, NX APIs + and initializeation APIs (as described below), and (2) timing. With NXSU, NX APIs execute immediately; with NXMU, NX APIs defer and serialize the operations and, hence, introduce different timing and potential race conditions that you would not experience with NXSU. diff --git a/Documentation/NuttxPortingGuide.html b/Documentation/NuttxPortingGuide.html index 65f4820bf04..89f9ff35f40 100644 --- a/Documentation/NuttxPortingGuide.html +++ b/Documentation/NuttxPortingGuide.html @@ -2257,7 +2257,7 @@ else

  • up_rtc_time(). Get the current time in seconds. This is similar to the standard time() function. This interface is only required if the low-resolution RTC/counter hardware implementation selected. - It is only used by the RTOS during intialization to set up the system time when CONFIG_RTC is set + It is only used by the RTOS during initializeation to set up the system time when CONFIG_RTC is set but neither CONFIG_RTC_HIRES nor CONFIG_RTC_DATETIME are set.
  • up_rtc_gettime(). @@ -3511,7 +3511,7 @@ extern void up_ledoff(int led);

    1. - Each USB host class driver includes an intialization entry point that is called from the + Each USB host class driver includes an initializeation entry point that is called from the application at initialization time. This driver calls usbhost_registerclass() during this initialization in order to makes itself available in the event the device that it supports is connected.

      @@ -3599,7 +3599,7 @@ extern void up_ledoff(int led);

      1. - Each USB device class driver includes an intialization entry point that is called from the + Each USB device class driver includes an initializeation entry point that is called from the application at initialization time.

        @@ -4134,7 +4134,7 @@ void pm_initialize(void);

        Description: This function is called by MCU-specific one-time at power on reset in order to initialize the power management capabilities. -This function must be called very early in the intialization sequence before any other device drivers are initialize (since they may attempt to register with the power management subsystem). +This function must be called very early in the initializeation sequence before any other device drivers are initialize (since they may attempt to register with the power management subsystem).

        Input Parameters: None diff --git a/Documentation/NuttxUserGuide.html b/Documentation/NuttxUserGuide.html index bedc07226c9..621c65c9397 100644 --- a/Documentation/NuttxUserGuide.html +++ b/Documentation/NuttxUserGuide.html @@ -1000,7 +1000,7 @@ int posix_spawn_file_actions_destroy(FAR posix_spawn_file_actions_t *file_action

        Description: - The posix_spawn_file_actions_destroy() function destroys the object referenced by file_actions which was previously intialized by posix_spawn_file_actions_init(), returning any resources obtained at the time of initialization to the system for subsequent reuse. + The posix_spawn_file_actions_destroy() function destroys the object referenced by file_actions which was previously initializeed by posix_spawn_file_actions_init(), returning any resources obtained at the time of initialization to the system for subsequent reuse. A posix_spawn_file_actions_t may be reinitialized after having been destroyed, but must not be reused after destruction, unless it has been reinitialized.