From d389819eea3a84e388935153e3be847342809da3 Mon Sep 17 00:00:00 2001 From: Amar Takhar Date: Mon, 18 Jan 2016 00:37:40 -0500 Subject: Convert all Unicode to ASCII(128) --- c_user/fatal_error.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'c_user/fatal_error.rst') diff --git a/c_user/fatal_error.rst b/c_user/fatal_error.rst index 2c540f1..b4c221a 100644 --- a/c_user/fatal_error.rst +++ b/c_user/fatal_error.rst @@ -81,7 +81,7 @@ contains three pieces of information: The error type indicator is dependent on the source of the error and whether or not the error was internally generated by the executive. If the error was generated -from an API, then the error code will be of that API’s +from an API, then the error code will be of that API's error or status codes. The status codes for the RTEMS API are in cpukit/rtems/include/rtems/rtems/status.h. Those for the POSIX API can be found in . @@ -106,8 +106,8 @@ occurred. Directives ========== -This section details the fatal error manager’s -directives. A subsection is dedicated to each of this manager’s +This section details the fatal error manager's +directives. A subsection is dedicated to each of this manager's directives and describes the calling sequence, related constants, usage, and status codes. @@ -137,7 +137,7 @@ error extension is defined in the configuration table, then the user-defined error extension is called. If configured and the provided FATAL error extension returns, then the RTEMS default error handler is invoked. This directive can be invoked by -RTEMS or by the user’s application code including initialization +RTEMS or by the user's application code including initialization tasks, other tasks, and ISRs. **NOTES:** -- cgit v1.2.3