Merge pull request #3512 from corob-msft/docs/corob/bad-ticks-part-1-of-n

PMEds28 · web-flow · commit c8ed2aec2cba · 2021-04-16T08:18:42.000+01:00
Bulk Fix: busted ticks.
diff --git a/docs/atl/reference/ccombstr-class.md b/docs/atl/reference/ccombstr-class.md
@@ -53,7 +53,7 @@ class CComBSTR
 |Name|Description|
 |----------|-----------------|
 |[CComBSTR::operator BSTR](#operator_bstr)|Casts a `CComBSTR` object to a BSTR.|
-|[CComBSTR::operator !](#operator_not)|Returns TRUE or FALSE, depending on whether `m_str`is NULL.|
+|[CComBSTR::operator !](#operator_not)|Returns TRUE or FALSE, depending on whether `m_str` is NULL.|
 |[CComBSTR::operator !=](#operator_neq)|Compares a `CComBSTR` with a string.|
 |[CComBSTR::operator &](#operator_amp)|Returns the address of `m_str`.|
 |[CComBSTR::operator +=](#operator_add_eq)|Appends a `CComBSTR` to the object.|
diff --git a/docs/build/reference/sourcedependencies-directives.md b/docs/build/reference/sourcedependencies-directives.md
@@ -19,7 +19,7 @@ This command-line option is similar to [`/sourceDependencies`](sourcedependencie
 - The output JSON file doesn't list imported modules and imported header units (*`.ifc`* files) because this switch does a scan of the project files, not a compilation. So there are no built modules or header units to list.
 - Only directly imported modules or header units are listed. It doesn't list the dependencies of the imported modules or header units themselves.
 - Header file dependencies are not listed. That is, `#include <file>` or `#include "file"` dependencies are not listed.
-- `/sourceDependencies:directives`is meant to be used before *`.ifc`* files are built.
+- `/sourceDependencies:directives` is meant to be used before *`.ifc`* files are built.
 
 ## Syntax
 
diff --git a/docs/c-runtime-library/reference/exp-expf.md b/docs/c-runtime-library/reference/exp-expf.md
@@ -93,5 +93,5 @@ exp( 2.302585 ) = 10.000000
 ## See also
 
 [Floating-Point Support](../../c-runtime-library/floating-point-support.md)\
-[l`og, logf, log10, log10f`](log-logf-log10-log10f.md)\
-[`_CIexp`](../../c-runtime-library/ciexp.md)
+[`log, logf, log10, log10f`](log-logf-log10-log10f.md)\
+[`_CIexp`](../../c-runtime-library/ciexp.md)
diff --git a/docs/c-runtime-library/reference/fmod-fmodf.md b/docs/c-runtime-library/reference/fmod-fmodf.md
@@ -95,5 +95,5 @@ The remainder of -10.00 / 3.00 is -1.000000
 [Floating-Point Support](../../c-runtime-library/floating-point-support.md)\
 [`ceil, ceilf, ceill`](ceil-ceilf-ceill.md)\
 [`fabs, fabsf, fabsl`](fabs-fabsf-fabsl.md)\
-[f`loor, floorf, floorl`](floor-floorf-floorl.md)\
-[`_CIfmod`](../../c-runtime-library/cifmod.md)
+[`floor, floorf, floorl`](floor-floorf-floorl.md)\
+[`_CIfmod`](../../c-runtime-library/cifmod.md)
diff --git a/docs/c-runtime-library/reference/freopen-s-wfreopen-s.md b/docs/c-runtime-library/reference/freopen-s-wfreopen-s.md
@@ -41,7 +41,7 @@ An out parameter that will point to the reopened stream when the function return
 *`fileName`*\
 Path of the file to reopen.
 
-*` mode`*\
+*`mode`*\
 The mode for the reopened stream.
 
 *`oldStream`*\
@@ -57,9 +57,9 @@ For more information about error codes, see [`errno, _doserrno, _sys_errlist, an
 
 The **`freopen_s`** function is typically used to attach the pre-opened streams associated with `stdin`, `stdout` and `stderr` to another file.
 
-The **`freopen_s`** function closes the file currently associated with *`stream`* and reassigns *`stream`* to the file specified by *path*. **`_wfreopen_s`** is a wide-character version of **`freopen_s`**; the *path* and *` mode`* arguments to **`_wfreopen_s`** are wide-character strings. **`_wfreopen_s`** and **`freopen_s`** behave identically otherwise.
+The **`freopen_s`** function closes the file currently associated with *`stream`* and reassigns *`stream`* to the file specified by *path*. **`_wfreopen_s`** is a wide-character version of **`freopen_s`**; the *path* and *`mode`* arguments to **`_wfreopen_s`** are wide-character strings. **`_wfreopen_s`** and **`freopen_s`** behave identically otherwise.
 
-If any of *pFile*, *path*, *` mode`*, or *`stream`* are **`NULL`**, or if *path* is an empty string, these functions invoke the invalid parameter handler, as described in [Parameter Validation](../../c-runtime-library/parameter-validation.md). If execution is allowed to continue, these functions set **`errno`** to **`EINVAL`** and return **`EINVAL`**.
+If any of *pFile*, *path*, *`mode`*, or *`stream`* are **`NULL`**, or if *path* is an empty string, these functions invoke the invalid parameter handler, as described in [Parameter Validation](../../c-runtime-library/parameter-validation.md). If execution is allowed to continue, these functions set **`errno`** to **`EINVAL`** and return **`EINVAL`**.
 
 By default, this function's global state is scoped to the application. To change this, see [Global state in the CRT](../global-state.md).
 
@@ -69,9 +69,9 @@ By default, this function's global state is scoped to the application. To change
 |---------------------|------------------------------------|--------------------|-----------------------|
 |**`_tfreopen_s`**|**`freopen_s`**|**`freopen_s`**|**`_wfreopen_s`**|
 
-**`freopen_s`** is typically used to redirect the pre-opened files **`stdin`**, **`stdout`**, and **`stderr`** to files specified by the user. The new file associated with *`stream`* is opened with *` mode`*, which is a character string specifying the type of access requested for the file, as follows:
+**`freopen_s`** is typically used to redirect the pre-opened files **`stdin`**, **`stdout`**, and **`stderr`** to files specified by the user. The new file associated with *`stream`* is opened with *`mode`*, which is a character string specifying the type of access requested for the file, as follows:
 
-|*` mode`*|Access|
+|*`mode`*|Access|
 |-|-|
 | **`"r"`** | Opens for reading. If the file doesn't exist or cannot be found, the **`freopen_s`** call fails. |
 | **`"w"`** | Opens an empty file for writing. If the given file exists, its contents are destroyed. |
@@ -86,16 +86,16 @@ When a file is opened with the **`"a"`** or **`"a+"`** access type, all write op
 
 The **`"a"`** mode doesn't remove the EOF marker before appending to the file. After appending has occurred, the MS-DOS TYPE command only shows data up to the original EOF marker and not any data appended to the file. The **`"a+"`** mode does remove the EOF marker before appending to the file. After appending, the MS-DOS TYPE command shows all data in the file. The **`"a+"`** mode is required for appending to a stream file that is terminated with the CTRL+Z EOF marker.
 
-When the **`"r+"`**, **`"w+"`**, or **`"a+"`** access type is specified, both reading and writing are allowed (the file is said to be open for "update"). However, when you switch between reading and writing, there must be an intervening [`fsetpos`](fsetpos.md), [`fseek`](fseek-fseeki64.md), or [`rewind`](rewind.md) operation. The current position can be specified for the [`fsetpos`](fsetpos.md) or [`fseek`](fseek-fseeki64.md) operation, if you want. In addition to the above values, one of the following characters may be included in the *` mode`* string to specify the translation mode for new lines.
+When the **`"r+"`**, **`"w+"`**, or **`"a+"`** access type is specified, both reading and writing are allowed (the file is said to be open for "update"). However, when you switch between reading and writing, there must be an intervening [`fsetpos`](fsetpos.md), [`fseek`](fseek-fseeki64.md), or [`rewind`](rewind.md) operation. The current position can be specified for the [`fsetpos`](fsetpos.md) or [`fseek`](fseek-fseeki64.md) operation, if you want. In addition to the above values, one of the following characters may be included in the *`mode`* string to specify the translation mode for new lines.
 
-|*` mode`* modifier|Translation mode|
+|*`mode`* modifier|Translation mode|
 |-|-|
 | **`t`** | Open in text (translated) mode. |
 | **`b`** | Open in binary (untranslated) mode; translations involving carriage-return and line feed characters are suppressed. |
 
 In text (translated) mode, carriage return-line feed (CR-LF) combinations are translated into single line feed (LF) characters on input; LF characters are translated to CR-LF combinations on output. Also, CTRL+Z is interpreted as an end-of-file character on input. In files opened for reading or for writing and reading with **`"a+"`**, the run-time library checks for a CTRL+Z at the end of the file and removes it, if possible. This is done because using [`fseek`](fseek-fseeki64.md) and [`ftell`](ftell-ftelli64.md) to move within a file may cause [`fseek`](fseek-fseeki64.md) to behave improperly near the end of the file. Don't use the **`t`** option when you want ANSI portability because it's a Microsoft extension.
 
-If **`t`** or **`b`** isn't given in *` mode`*, the default translation mode is defined by the global variable [`_fmode`](../../c-runtime-library/fmode.md). If **`t`** or **`b`** is prefixed to the argument, the function fails and returns **`NULL`**.
+If **`t`** or **`b`** isn't given in *`mode`*, the default translation mode is defined by the global variable [`_fmode`](../../c-runtime-library/fmode.md). If **`t`** or **`b`** is prefixed to the argument, the function fails and returns **`NULL`**.
 
 For a discussion of text and binary modes, see [Text and Binary Mode File I/O](../../c-runtime-library/text-and-binary-mode-file-i-o.md).
 
@@ -106,7 +106,7 @@ For a discussion of text and binary modes, see [Text and Binary Mode File I/O](.
 |**`freopen_s`**|`<stdio.h>`|
 |**`_wfreopen_s`**|`<stdio.h>` or `<wchar.h>`|
 
-The console isn't supported in Universal Windows Platform (UWP) apps. The standard stream handles that are associated with the console, **`stdin`**, **`stdout`**, and **`stderr`**, must be redirected before C run-time functions can use them in UWP apps. 
+The console isn't supported in Universal Windows Platform (UWP) apps. The standard stream handles that are associated with the console, **`stdin`**, **`stdout`**, and **`stderr`**, must be redirected before C run-time functions can use them in UWP apps.
 
 For more compatibility information, see [Compatibility](../../c-runtime-library/compatibility.md).
 
@@ -153,6 +153,6 @@ This will go to the file 'freopen.out'
 [`fclose, _fcloseall`](fclose-fcloseall.md)\
 [`_fdopen, _wfdopen`](fdopen-wfdopen.md)\
 [`_fileno`](fileno.md)\
-[`fopen, _wfope`n](fopen-wfopen.md)\
+[`fopen, _wfopen`](fopen-wfopen.md)\
 [`_open, _wopen`](open-wopen.md)\
 [`_setmode`](setmode.md)
diff --git a/docs/code-quality/c6273.md b/docs/code-quality/c6273.md
@@ -15,7 +15,7 @@ This warning indicates that the format string specifies an integer, for example,
 
 ## Example
 
-The following code generates this warning because an integer is required instead of a **`float`** to `sprintf` function:
+The following code generates this warning because an integer is required instead of a **`float`** in the `sprintf` function:
 
 ```cpp
 #include <stdio.h>
@@ -64,4 +64,4 @@ This warning is not applicable on Windows 9x and Windows NT version 4 because %p
 
 ## See also
 
-[sprintf, _sprintf_l, swprintf, _swprintf_l, \__swprintf_l](../c-runtime-library/reference/sprintf-sprintf-l-swprintf-swprintf-l-swprintf-l.md)
+[`sprintf, _sprintf_l, swprintf, _swprintf_l, __swprintf_l`](../c-runtime-library/reference/sprintf-sprintf-l-swprintf-swprintf-l-swprintf-l.md)
diff --git a/docs/cppcx/namespaces-reference-c-cx.md b/docs/cppcx/namespaces-reference-c-cx.md
@@ -19,7 +19,7 @@ To simplify the coding of programs that target the Windows Runtime, the C++/CX c
 |-----------|-----------------|
 |[default namespace](../cppcx/default-namespace.md)|Contains descriptions of built-in, fundamental types.|
 |[Platform namespace](../cppcx/platform-namespace-c-cx.md)|Contains descriptions of types that you can use, and also internal types that are used only by the compiler infrastructure.|
-|[Windows::Foundation::Collections Namespace](../cppcx/windows-foundation-collections-namespace-c-cx.md)|Contains descriptions of enhancements and extensions to the Windows Runtime`Windows::Foundation::Collections` namespace.|
+|[Windows::Foundation::Collections Namespace](../cppcx/windows-foundation-collections-namespace-c-cx.md)|Contains descriptions of enhancements and extensions to the Windows Runtime `Windows::Foundation::Collections` namespace.|
 
 ## See also
 
diff --git a/docs/cppcx/platform-collections-vectorviewiterator-class.md b/docs/cppcx/platform-collections-vectorviewiterator-class.md
@@ -9,7 +9,7 @@ ms.assetid: be3aa1ae-e6ba-4a06-8d6b-86d8128026f7
 ---
 # Platform::Collections::VectorViewIterator Class
 
-Provides a Standard Template Library iterator for objects derived from the Windows Runtime`IVectorView` interface.
+Provides a Standard Template Library iterator for objects derived from the Windows Runtime `IVectorView` interface.
 
 `ViewVectorIterator` is a proxy iterator that stores elements of type `VectorProxy<T>`. However, the proxy object is almost never visible to user code. For more information, see [Collections (C++/CX)](../cppcx/collections-c-cx.md).
 
diff --git a/docs/cppcx/ref-classes-and-structs-c-cx.md b/docs/cppcx/ref-classes-and-structs-c-cx.md
@@ -24,7 +24,7 @@ A ref class or ref struct has these essential features:
 
 ## Declaration
 
-The following code fragment declares the `Person` ref class. Notice that the standard C++ `std::map` type is used in the private members, and the Windows Runtime`IMapView` interface is used in the public interface. Also notice that the "^" is appended to declarations of reference types.
+The following code fragment declares the `Person` ref class. Notice that the standard C++ `std::map` type is used in the private members, and the Windows Runtime `IMapView` interface is used in the public interface. Also notice that the "^" is appended to declarations of reference types.
 
 [!code-cpp[cx_classes#03](../cppcx/codesnippet/CPP/classesstructs/class1.h#03)]
 
diff --git a/docs/mfc/reference/cdbexception-class.md b/docs/mfc/reference/cdbexception-class.md
@@ -61,7 +61,7 @@ This type includes SQL-prefixed codes defined by ODBC and AFX_SQL-prefixed codes
 
 - AFX_SQL_ERROR_API_CONFORMANCE The driver for a `CDatabase::OpenEx` or `CDatabase::Open` call does not conform to required ODBC API Conformance level 1 ( SQL_OAC_LEVEL1).
 
-- AFX_SQL_ERROR_CONNECT_FAIL Connection to the data source failed. You passed a NULL`CDatabase` pointer to your recordset constructor and the subsequent attempt to create a connection based on `GetDefaultConnect` failed.
+- AFX_SQL_ERROR_CONNECT_FAIL Connection to the data source failed. You passed a NULL `CDatabase` pointer to your recordset constructor and the subsequent attempt to create a connection based on `GetDefaultConnect` failed.
 
 - AFX_SQL_ERROR_DATA_TRUNCATED You requested more data than you have provided storage for. For information on increasing the provided data storage for `CString` or `CByteArray` data types, see the `nMaxLength` argument for [RFX_Text](record-field-exchange-functions.md#rfx_text) and [RFX_Binary](record-field-exchange-functions.md#rfx_binary) under "Macros and Globals."
 
diff --git a/docs/mfc/reference/cmenu-class.md b/docs/mfc/reference/cmenu-class.md
@@ -793,7 +793,7 @@ The *nMaxCount* parameter should be one larger than the number of characters in
 
 ## <a name="getsafehmenu"></a> CMenu::GetSafeHmenu
 
-Returns the HMENU wrapped by this `CMenu` object, or a NULL`CMenu` pointer.
+Returns the HMENU wrapped by this `CMenu` object, or a NULL `CMenu` pointer.
 
 ```
 HMENU GetSafeHmenu() const;
diff --git a/docs/parallel/concrt/creating-asynchronous-operations-in-cpp-for-windows-store-apps.md b/docs/parallel/concrt/creating-asynchronous-operations-in-cpp-for-windows-store-apps.md
@@ -63,7 +63,7 @@ The notion of an *action* means that the asynchronous task doesn't produce a val
 
 The return type of `create_async` is determined by the type of its arguments. For example, if your work function doesn't return a value and doesn't report progress, `create_async` returns `IAsyncAction`. If your work function doesn't return a value and also reports progress, `create_async` returns `IAsyncActionWithProgress`. To report progress, provide a [concurrency::progress_reporter](../../parallel/concrt/reference/progress-reporter-class.md) object as the parameter to your work function. The ability to report progress enables you to report what amount of work was performed and what amount still remains (for example, as a percentage). It also enables you to report results as they become available.
 
-The `IAsyncAction`, `IAsyncActionWithProgress<TProgress>`, `IAsyncOperation<TResult>`, and `IAsyncActionOperationWithProgress<TProgress, TProgress>` interfaces each provide a `Cancel` method that enables you to cancel the asynchronous operation. The `task` class works with cancellation tokens. When you use a cancellation token to cancel work, the runtime does not start new work that subscribes to that token. Work that is already active can monitor its cancellation token and stop when it can. This mechanism is described in greater detail in the document [Cancellation in the PPL](cancellation-in-the-ppl.md). You can connect task cancellation with the Windows Runtime`Cancel` methods in two ways. First, you can define the work function that you pass to `create_async` to take a [concurrency::cancellation_token](../../parallel/concrt/reference/cancellation-token-class.md) object. When the `Cancel` method is called, this cancellation token is canceled and the normal cancellation rules apply to the underlying `task` object that supports the `create_async` call. If you do not provide a `cancellation_token` object, the underlying `task` object defines one implicitly. Define a `cancellation_token` object when you need to cooperatively respond to cancellation in your work function. The section [Example: Controlling Execution in a Windows Runtime App with C++ and XAML](#example-app) shows an example of how to perform cancellation in a Universal Windows Platform (UWP) app with C# and XAML that uses a custom Windows Runtime C++ component.
+The `IAsyncAction`, `IAsyncActionWithProgress<TProgress>`, `IAsyncOperation<TResult>`, and `IAsyncActionOperationWithProgress<TProgress, TProgress>` interfaces each provide a `Cancel` method that enables you to cancel the asynchronous operation. The `task` class works with cancellation tokens. When you use a cancellation token to cancel work, the runtime does not start new work that subscribes to that token. Work that is already active can monitor its cancellation token and stop when it can. This mechanism is described in greater detail in the document [Cancellation in the PPL](cancellation-in-the-ppl.md). You can connect task cancellation with the Windows Runtime `Cancel` methods in two ways. First, you can define the work function that you pass to `create_async` to take a [concurrency::cancellation_token](../../parallel/concrt/reference/cancellation-token-class.md) object. When the `Cancel` method is called, this cancellation token is canceled and the normal cancellation rules apply to the underlying `task` object that supports the `create_async` call. If you do not provide a `cancellation_token` object, the underlying `task` object defines one implicitly. Define a `cancellation_token` object when you need to cooperatively respond to cancellation in your work function. The section [Example: Controlling Execution in a Windows Runtime App with C++ and XAML](#example-app) shows an example of how to perform cancellation in a Universal Windows Platform (UWP) app with C# and XAML that uses a custom Windows Runtime C++ component.
 
 > [!WARNING]
 > In a chain of task continuations, always clean up state and then call [concurrency::cancel_current_task](reference/concurrency-namespace-functions.md#cancel_current_task) when the cancellation token is canceled. If you return early instead of calling `cancel_current_task`, the operation transitions to the completed state instead of the canceled state.
