Merge pull request #4769 from corob-msft/learn/corob/ucrt_f1_r4

Fixing UCRT F1 issues 4 of many

Author: prmerger-automator[bot]

docs/c-runtime-library/reference/fsopen-wfsopen.md

@@ -80,7 +80,6 @@ The argument *`shflag`* is a constant expression consisting of one of the follow
 
 | Term | Definition |
 |---|---|
-| `_SH_COMPAT` | Sets Compatibility mode for 16-bit applications. |
 | `_SH_DENYNO` | Permits read and write access. |
 | `_SH_DENYRD` | Denies read access to the file. |
 | `_SH_DENYRW` | Denies read and write access to the file. |

docs/c-runtime-library/reference/signal.md

@@ -56,7 +56,7 @@ By default, **`signal`** terminates the calling program with exit code 3, regard
 > [!NOTE]
 > `SIGINT` is not supported for any Win32 application. When a CTRL+C interrupt occurs, Win32 operating systems generate a new thread to specifically handle that interrupt. This can cause a single-thread application, such as one in UNIX, to become multithreaded and cause unexpected behavior.
 
-The *`func`* argument is an address to a signal handler that you write, or to one of the predefined constants `SIG_DFL` or `SIG_IGN`, which are also defined in SIGNAL.H. If *`func`* is a function, it's installed as the signal handler for the given signal. The signal handler's prototype requires one formal argument, *`sig`*, of type **`int`**. The operating system provides the actual argument through *`sig`* when an interrupt occurs; the argument is the signal that generated the interrupt. Therefore, you can use the six manifest constants (listed in the preceding table) in your signal handler to determine which interrupt occurred and take appropriate action. For example, you can call **`signal`** twice to assign the same handler to two different signals, and then test the *`sig`* argument in the handler to take different actions based on the signal received.
+The *`func`* argument is an address to a signal handler that you write, or to one of the predefined [signal action constants](../signal-action-constants.md) `SIG_DFL` or `SIG_IGN`, which are also defined in SIGNAL.H. If *`func`* is a function, it's installed as the signal handler for the given signal. The signal handler's prototype requires one formal argument, *`sig`*, of type **`int`**. The operating system provides the actual argument through *`sig`* when an interrupt occurs; the argument is the signal that generated the interrupt. Therefore, you can use the six manifest constants (listed in the preceding table) in your signal handler to determine which interrupt occurred and take appropriate action. For example, you can call **`signal`** twice to assign the same handler to two different signals, and then test the *`sig`* argument in the handler to take different actions based on the signal received.
 
 If you're testing for floating-point exceptions (`SIGFPE`), *`func`* points to a function that takes an optional second argument that is one of several manifest constants, defined in `FLOAT.H`, of the form `FPE_xxx`. When a `SIGFPE` signal occurs, you can test the value of the second argument to determine the kind of floating-point exception, and then take appropriate action. This argument and its possible values are Microsoft extensions.
 

docs/c-runtime-library/sbcs-and-mbcs-data-types.md

@@ -3,7 +3,7 @@ title: "SBCS and MBCS Data Types"
 description: "How to represent single and multibyte characters in the Microsoft C runtime."
 ms.topic: "conceptual"
 ms.date: "04/11/2018"
-f1_keywords: ["MBCS", "SBCS"]
+f1_keywords: ["_MBCS", "MBCS", "SBCS"]
 helpviewer_keywords: ["SBCS and MBCS data types", "data types [C], MBCS and SBCS"]
 ms.assetid: 4c3ef9da-e397-48d4-800e-49dba36db171
 ---

docs/c-runtime-library/security-features-in-the-crt.md

@@ -3,7 +3,7 @@ title: "Security Features in the CRT"
 description: "An overview of secure CRT functions in the Microsoft C runtime."
 ms.date: "09/29/2020"
 ms.topic: "conceptual"
-f1_keywords: ["_CRT_SECURE_NO_DEPRECATE", "_CRT_NONSTDC_NO_WARNINGS", "_CRT_SECURE_NO_WARNINGS"]
+f1_keywords: ["_CRT_SECURE_NO_DEPRECATE", "_CRT_NONSTDC_NO_DEPRECATE", "_CRT_NONSTDC_NO_WARNINGS", "_CRT_SECURE_NO_WARNINGS"]
 helpviewer_keywords: ["security deprecation warnings [C++]", "CRT_NONSTDC_NO_DEPRECATE", "buffers [C++], buffer overruns", "deprecation warnings (security-related), disabling", "_CRT_NONSTDC_NO_WARNINGS", "security [CRT]", "_CRT_SECURE_NO_WARNINGS", "_CRT_NONSTDC_NO_DEPRECATE", "_CRT_SECURE_NO_DEPRECATE", "security-enhanced CRT", "CRT_SECURE_NO_WARNINGS", "CRT_SECURE_NO_DEPRECATE", "deprecation warnings (security-related)", "buffer overruns", "CRT_NONSTDC_NO_WARNINGS", "CRT, security enhancements", "parameters [C++], validation"]
 ms.assetid: d9568b08-9514-49cd-b3dc-2454ded195a3
 ---

docs/c-runtime-library/set-app-type.md

@@ -6,7 +6,7 @@ api_name: ["_set_app_type", "_o__set_app_type"]
 api_location: ["api-ms-win-crt-runtime-l1-1-0.dll"]
 api_type: ["DLLExport"]
 topic_type: ["apiref"]
-f1_keywords: ["_set_app_type", "corecrt_startup/_set_app_type"]
+f1_keywords: ["_set_app_type", "corecrt_startup/_set_app_type", "corecrt_startup/_crt_app_type", "corecrt_startup/_crt_unknown_app", "corecrt_startup/_crt_console_app", "corecrt_startup/_crt_gui_app"]
 ms.assetid: 1e7fe786-b587-4116-8c05-f7d762350100
 ---
 # `_set_app_type`

docs/c-runtime-library/setvbuf-constants.md

@@ -2,7 +2,7 @@
 description: "Learn more about: setvbuf Constants"
 title: "setvbuf Constants"
 ms.date: "11/04/2016"
-f1_keywords: ["_IOFBF", "_IONBF", "_IOLBF"]
+f1_keywords: ["STDIO/_IOFBF", "STDIO/_IONBF", "STDIO/_IOLBF", "_IOFBF", "_IONBF", "_IOLBF"]
 helpviewer_keywords: ["_IOFBF constant", "IOFBF constant", "IONBF constant", "_IOLBF constant", "IOLBF constant", "_IONBF constant"]
 ms.assetid: a6ec4dd5-1f24-498c-871a-e874cd28d33c
 ---

docs/c-runtime-library/sharing-constants.md

@@ -2,8 +2,8 @@
 description: "Learn more about: Sharing Constants"
 title: "Sharing Constants"
 ms.date: "11/04/2016"
-f1_keywords: ["_SH_DENYNO", "_SH_DENYRD", "_SH_DENYRW", "_SH_DENYWR", "_SH_COMPAT"]
-helpviewer_keywords: ["_SH_DENYRW constant", "SH_DENYRD constant", "_SH_COMPAT constant", "_SH_DENYRD constant", "SH_DENYRW constant", "sharing constants", "SH_DENYNO constant", "_SH_DENYWR constant", "SH_DENYWR constant", "_SH_DENYNO constant", "SH_COMPAT constant"]
+f1_keywords: ["CORECRT_SHARE/_SH_DENYNO", "CORECRT_SHARE/_SH_DENYRD", "CORECRT_SHARE/_SH_DENYRW", "CORECRT_SHARE/_SH_DENYWR", "CORECRT_SHARE/_SH_SECURE", "_SH_DENYNO", "_SH_DENYRD", "_SH_DENYRW", "_SH_DENYWR", "_SH_SECURE"]
+helpviewer_keywords: ["_SH_DENYRW constant", "SH_DENYRD constant", "_SH_SECURE constant", "_SH_DENYRD constant", "SH_DENYRW constant", "sharing constants", "SH_DENYNO constant", "_SH_DENYWR constant", "SH_DENYWR constant", "_SH_DENYNO constant", "SH_SECURE constant"]
 ms.assetid: 95fadc3a-55dc-473d-98b5-e8211900465d
 ---
 # Sharing constants

docs/c-runtime-library/signal-action-constants.md

@@ -2,7 +2,7 @@
 description: "Learn more about: signal Action Constants"
 title: "signal Action Constants"
 ms.date: "11/04/2016"
-f1_keywords: ["SIG_IGN", "SIG_DFL"]
+f1_keywords: ["SIGNAL/SIG_IGN", "SIGNAL/SIG_DFL", "SIGNAL/SIG_GET", "SIGNAL/SIG_SGE", "SIGNAL/SIG_ACK", "SIGNAL/SIG_ERR", "SIG_IGN", "SIG_DFL", "SIG_GET", "SIG_SGE", "SIG_ACK", "SIG_ERR"]
 helpviewer_keywords: ["signal action constants", "SIG_IGN constant", "SIG_DFL constant"]
 ms.assetid: c3cb4f15-d39e-4d9d-84f9-0d33e3eb5993
 ---
@@ -24,6 +24,7 @@ The `func` argument must be either a function address or one of the manifest con
 |---|---|
 | `SIG_DFL` | Uses system-default response. If the calling program uses stream I/O, buffers created by the run-time library aren't flushed. |
 | `SIG_IGN` | Ignores interrupt signal. This value should never be given for `SIGFPE`, since the floating-point state of the process is left undefined. |
+| `SIG_GET` | Returns the current value of the signal. |
 | `SIG_SGE` | Indicates an error occurred in the signal. |
 | `SIG_ACK` | Indicates an acknowledgment was received. |
 | `SIG_ERR` | A return type from a signal indicating an error has occurred. |

docs/c-runtime-library/signal-constants.md

@@ -2,7 +2,7 @@
 description: "Learn more about: signal Constants"
 title: "signal Constants"
 ms.date: "11/04/2016"
-f1_keywords: ["SIGTERM", "SIGFPE", "SIGABRT", "SIGILL", "SIGINT", "SIGSEGV"]
+f1_keywords: ["SIGNAL/SIGTERM", "SIGNAL/SIGFPE", "SIGNAL/SIGABRT", "SIGNAL/SIGILL", "SIGNAL/SIGINT", "SIGNAL/SIGSEGV", "SIGNAL/SIGABRT_COMPAT", "SIGTERM", "SIGFPE", "SIGABRT", "SIGILL", "SIGINT", "SIGSEGV", "SIGABRT_COMPAT"]
 helpviewer_keywords: ["SIGTERM constant", "SIGABRT constant", "SIGSEGV constant", "SIGFPE constant", "SIGINT constant", "signal constants", "SIGILL constant"]
 ms.assetid: a3b39281-dae7-4e44-8d68-e6a610c669dd
 ---
@@ -21,7 +21,7 @@ The `sig` argument must be one of the manifest constants listed below (defined i
 | Constant | Description |
 |---|---|
 | `SIGABRT` | Abnormal termination. The default action terminates the calling program with exit code 3. |
-| `SIGABRT_COMPAT` | Same as `SIGABRT`. For compatibility with other platforms. |
+| `SIGABRT_COMPAT` | Same meaning as `SIGABRT`. For compatibility with other platforms. |
 | `SIGFPE` | Floating-point error, such as overflow, division by zero, or invalid operation. The default action terminates the calling program. |
 | `SIGILL` | Illegal instruction. The default action terminates the calling program. |
 | `SIGINT` | CTRL+C interrupt. The default action terminates the calling program with exit code 3. |