Merge pull request MicrosoftDocs#1927 from Saisang/sai-removetag-bloc…

…kquate-18

Bulk update to remove tag <blockquate> 18

desktop-src/ProcThread/zwqueryinformationprocess.md

@@ -62,7 +62,7 @@ The type of process information to be retrieved. This parameter can be one of th
 | <span id="ProcessDebugPort"></span><span id="processdebugport"></span><span id="PROCESSDEBUGPORT"></span><dl><dt><strong>ProcessDebugPort</strong></dt><dt>7</dt></dl> | Retrieves a <strong>DWORD_PTR</strong> value that is the port number of the debugger for the process. A nonzero value indicates that the process is being run under the control of a ring 3 debugger.<br /> It is best to use the <a href="/windows/desktop/api/debugapi/nf-debugapi-checkremotedebuggerpresent"><strong>CheckRemoteDebuggerPresent</strong></a> or <a href="/windows/desktop/api/debugapi/nf-debugapi-isdebuggerpresent"><strong>IsDebuggerPresent</strong></a> function.<br /> |
 | <span id="ProcessWow64Information"></span><span id="processwow64information"></span><span id="PROCESSWOW64INFORMATION"></span><dl><dt><strong>ProcessWow64Information</strong></dt><dt>26</dt></dl> | Determines whether the process is running in the WOW64 environment (WOW64 is the x86 emulator that allows Win32-based applications to run on 64-bit Windows).<br /> It is best to use the <a href="/windows/desktop/api/wow64apiset/nf-wow64apiset-iswow64process"><strong>IsWow64Process</strong></a> function to obtain this information.<br /> |
 | <span id="ProcessImageFileName"></span><span id="processimagefilename"></span><span id="PROCESSIMAGEFILENAME"></span><dl><dt><strong>ProcessImageFileName</strong></dt><dt>27</dt></dl> | Retrieves a <strong>UNICODE_STRING</strong> value containing the name of the image file for the process.<br /> |
-| <span id="ProcessBreakOnTermination"></span><span id="processbreakontermination"></span><span id="PROCESSBREAKONTERMINATION"></span><dl><dt><strong>ProcessBreakOnTermination</strong></dt><dt>29</dt></dl> | Retrieves a <strong>ULONG</strong> value indicating whether the process is considered critical.<br /><blockquote>[!Note]<br />This value can be used starting in Windows XP with SP3. Starting in Windows 8.1, <a href="/windows/desktop/api/processthreadsapi/nf-processthreadsapi-isprocesscritical"><strong>IsProcessCritical</strong></a> should be used instead.</blockquote><br /> |
+| **ProcessBreakOnTermination**<br>29<br> | Retrieves a **ULONG** value indicating whether the process is considered critical.<br> **Note:** This value can be used starting in Windows XP with SP3. Starting in Windows 8.1, [**IsProcessCritical**](/windows/desktop/api/processthreadsapi/nf-processthreadsapi-isprocesscritical) should be used instead.<br> |
 | <span id="ProcessProtectionInformation"></span><span id="processprotectioninformation"></span><span id="PROCESSPROTECTIONINFORMATION"></span><dl><dt><strong>ProcessProtectionInformation</strong></dt><dt>61</dt></dl> | Retrieves a BYTE value indicating the type of protected process and the protected process signer.<br /> |
 
 

desktop-src/Rpc/interface-registration-flags.md

@@ -30,13 +30,13 @@ The following constants are used in the *Flags* parameter of the [**RpcServerReg
 | Constant | Description | 
 |----------|-------------|
 | <span id="0"></span><dl><dt><strong>0</strong></dt></dl> | Standard interface semantics.<br /> | 
-| <span id="RPC_IF_ALLOW_CALLBACKS_WITH_NO_AUTH"></span><span id="rpc_if_allow_callbacks_with_no_auth"></span><dl><dt><strong>RPC_IF_ALLOW_CALLBACKS_WITH_NO_AUTH</strong></dt></dl> | When this interface flag is registered, the RPC runtime invokes the registered security callback for all calls, regardless of identity, protocol sequence, or authentication level of the client.<br /><blockquote>[!Note]<br />This flag is available starting with Windows XP with SP2 and Windows Server 2003 with SP1. When this flag is not set, RPC automatically filters all unauthenticated calls before they reach the security callback.</blockquote><br /> | 
-| <span id="RPC_IF_ALLOW_LOCAL_ONLY"></span><span id="rpc_if_allow_local_only"></span><dl><dt><strong>RPC_IF_ALLOW_LOCAL_ONLY</strong></dt></dl> | When this interface flag is registered, the RPC runtime rejects calls made by remote clients. All local calls using ncadg_* and ncacn_* protocol sequences are also rejected, with the exception of ncacn_np. RPC allows ncacn_NP calls only if the call does not come from SRV. Calls from ncalrpc are always processed.<br /><blockquote>[!Note]<br />This flag is available starting with Windows XP with SP2 and Windows Server 2003 with SP1.</blockquote><br /> | 
+| **RPC_IF_ALLOW_CALLBACKS_WITH_NO_AUTH**<br> | When this interface flag is registered, the RPC runtime invokes the registered security callback for all calls, regardless of identity, protocol sequence, or authentication level of the client.<br> **Note:** This flag is available starting with Windows XP with SP2 and Windows Server 2003 with SP1. When this flag is not set, RPC automatically filters all unauthenticated calls before they reach the security callback.<br> | 
+| **RPC_IF_ALLOW_LOCAL_ONLY**<br> | When this interface flag is registered, the RPC runtime rejects calls made by remote clients. All local calls using ncadg_* and ncacn_* protocol sequences are also rejected, with the exception of ncacn_np. RPC allows ncacn_NP calls only if the call does not come from SRV. Calls from ncalrpc are always processed.<br> **Note:** This flag is available starting with Windows XP with SP2 and Windows Server 2003 with SP1.<br> | 
 | <span id="RPC_IF_AUTOLISTEN"></span><span id="rpc_if_autolisten"></span><dl><dt><strong>RPC_IF_AUTOLISTEN</strong></dt></dl> | This is an <strong>auto-listen</strong> interface. The run time begins listening for calls as soon as the first autolisten interface is registered, and stops listening when the last autolisten interface is unregistered.<br /> | 
 | <span id="RPC_IF_OLE"></span><span id="rpc_if_ole"></span><dl><dt><strong>RPC_IF_OLE</strong></dt></dl> | Reserved for OLE. Do not use this flag.<br /> | 
 | <span id="RPC_IF_ALLOW_UNKNOWN_AUTHORITY"></span><span id="rpc_if_allow_unknown_authority"></span><dl><dt><strong>RPC_IF_ALLOW_UNKNOWN_AUTHORITY</strong></dt></dl> | Currently not implemented.<br /> | 
 | <span id="RPC_IF_ALLOW_SECURE_ONLY"></span><span id="rpc_if_allow_secure_only"></span><dl><dt><strong>RPC_IF_ALLOW_SECURE_ONLY</strong></dt></dl> | Limits connections to clients that use an authorization level higher than RPC_C_AUTHN_LEVEL_NONE. Specifying this flag allows clients to come through on the <strong>NULL</strong> session. On Windows XP and Windows Server 2003, such clients are not allowed. Clients that fail the RPC_IF_ALLOW_SECURE_ONLY test receive an RPC_S_ACCESS_DENIED error. Using the RPC_IF_ALLOW_SECURE_ONLY flag does not imply or guarantee a high level of privilege on the part of the calling user. RPC only checks that the user has valid credentials; the calling user may be using the guest account or other low privileged accounts. Do not assume high privilege when RPC_IF_ALLOW_SECURE_ONLY is used.<br /><strong>Windows NT 4.0 and Windows Me/98/95:  </strong><br /> | 
-| <span id="RPC_IF_SEC_NO_CACHE"></span><span id="rpc_if_sec_no_cache"></span><dl><dt><strong>RPC_IF_SEC_NO_CACHE</strong></dt></dl> | Disables security callback caching, forcing a security callback for each RPC call on a given interface.<br /><blockquote>[!Note]<br />This flag is available starting with Windows XP with SP2 and Windows Server 2003 with SP1.</blockquote><br /> | 
+| **RPC_IF_SEC_NO_CACHE**<br> | Disables security callback caching, forcing a security callback for each RPC call on a given interface.<br> **Note:** This flag is available starting with Windows XP with SP2 and Windows Server 2003 with SP1.<br> | 
 
 
 

desktop-src/SecAuthN/decryptmessage--digest.md

@@ -53,7 +53,7 @@ This parameter can be one of the following flags.
 
 | Value | Meaning | 
 |-------|---------|
-| <span id="SECQOP_WRAP_NO_ENCRYPT"></span><span id="secqop_wrap_no_encrypt"></span><dl><dt><strong>SECQOP_WRAP_NO_ENCRYPT</strong></dt></dl> | The message was not encrypted, but a header or trailer was produced.<br /><blockquote>[!Note]<br />KERB_WRAP_NO_ENCRYPT has the same value and the same meaning.</blockquote><br /> | 
+| **SECQOP_WRAP_NO_ENCRYPT**<br> | The message was not encrypted, but a header or trailer was produced.<br> **Note:** KERB_WRAP_NO_ENCRYPT has the same value and the same meaning.<br> | 
 | <span id="SIGN_ONLY_"></span><span id="sign_only_"></span><dl><dt><strong>SIGN_ONLY</strong></dt></dl> | When using the Digest SSP, use this flag when the [*security context*](../secgloss/s-gly.md) is set to verify the [*signature*](../secgloss/s-gly.md) only. For more information, see [Quality of Protection](quality-of-protection.md).<br /> | 
 
 

desktop-src/SecAuthN/decryptmessage--general.md

@@ -96,7 +96,7 @@ This parameter can be one of the following flags.
 
 | Value | Meaning | 
 |-------|---------|
-| <span id="SECQOP_WRAP_NO_ENCRYPT"></span><span id="secqop_wrap_no_encrypt"></span><dl><dt><strong>SECQOP_WRAP_NO_ENCRYPT</strong></dt></dl> | The message was not encrypted, but a header or trailer was produced.<br /><blockquote>[!Note]<br />KERB_WRAP_NO_ENCRYPT has the same value and the same meaning.</blockquote><br /> | 
+| **SECQOP_WRAP_NO_ENCRYPT**<br> | The message was not encrypted, but a header or trailer was produced.<br> **Note:** KERB_WRAP_NO_ENCRYPT has the same value and the same meaning.<br> | 
 | <span id="SIGN_ONLY_"></span><span id="sign_only_"></span><dl><dt><strong>SIGN_ONLY</strong></dt></dl> | When using the Digest SSP, use this flag when the [*security context*](../secgloss/s-gly.md) is set to verify the [*signature*](../secgloss/s-gly.md) only. For more information, see [Quality of Protection](quality-of-protection.md).<br /> | 
 
 

desktop-src/SecAuthN/decryptmessage--negotiate.md

@@ -47,7 +47,7 @@ This parameter can be the following flag.
 
 | Value | Meaning | 
 |-------|---------|
-| <span id="SECQOP_WRAP_NO_ENCRYPT"></span><span id="secqop_wrap_no_encrypt"></span><dl><dt><strong>SECQOP_WRAP_NO_ENCRYPT</strong></dt></dl> | The message was not encrypted, but a header or trailer was produced.<br /><blockquote>[!Note]<br />KERB_WRAP_NO_ENCRYPT has the same value and the same meaning.</blockquote><br /> | 
+| **SECQOP_WRAP_NO_ENCRYPT**<br> | The message was not encrypted, but a header or trailer was produced.<br> **Note:** KERB_WRAP_NO_ENCRYPT has the same value and the same meaning.<br> | 
 
 
 ## Return value

desktop-src/SecAuthN/decryptmessage--ntlm.md

@@ -47,7 +47,7 @@ This parameter can be the following flag.
 
 | Value | Meaning | 
 |-------|---------|
-| <span id="SECQOP_WRAP_NO_ENCRYPT"></span><span id="secqop_wrap_no_encrypt"></span><dl><dt><strong>SECQOP_WRAP_NO_ENCRYPT</strong></dt></dl> | The message was not encrypted, but a header or trailer was produced.<br /><blockquote>[!Note]<br />KERB_WRAP_NO_ENCRYPT has the same value and the same meaning.</blockquote><br /> | 
+| **SECQOP_WRAP_NO_ENCRYPT**<br> | The message was not encrypted, but a header or trailer was produced.<br> **Note:** KERB_WRAP_NO_ENCRYPT has the same value and the same meaning.<br> | 
 
 
 ## Return value

desktop-src/SecAuthN/decryptmessage--schannel.md

@@ -58,7 +58,7 @@ This parameter can be the following flag.
 
 | Value | Meaning | 
 |-------|---------|
-| <span id="SECQOP_WRAP_NO_ENCRYPT"></span><span id="secqop_wrap_no_encrypt"></span><dl><dt><strong>SECQOP_WRAP_NO_ENCRYPT</strong></dt></dl> | The message was not encrypted, but a header or trailer was produced.<br /><blockquote>[!Note]<br />KERB_WRAP_NO_ENCRYPT has the same value and the same meaning.</blockquote><br /> | 
+| **SECQOP_WRAP_NO_ENCRYPT**<br> | The message was not encrypted, but a header or trailer was produced.<br> **Note:** KERB_WRAP_NO_ENCRYPT has the same value and the same meaning.<br> | 
 
 
 ## Return value

desktop-src/printdocs/printer-driver-installation-reference.md

@@ -19,8 +19,8 @@ The functions in this section install and configure printer drivers on a compute
 |----------|-------------|
 | <a href="addmonitor.md"><strong>AddMonitor</strong></a><br /> | The <a href="/windows/desktop/printdocs/addmonitor"><strong>AddMonitor</strong></a> function installs a local port monitor and links the configuration, data, and monitor files.<br /> | 
 | <a href="addport.md"><strong>AddPort</strong></a><br /> | The <a href="/windows/desktop/printdocs/addport"><strong>AddPort</strong></a> function adds the name of a port to the list of supported ports. The <strong>AddPort</strong> function is exported by the port monitor.<br /> | 
-| <a href="addprinterdriver.md"><strong>AddPrinterDriver</strong></a><br /> | The <a href="/windows/desktop/printdocs/addprinterdriver"><strong>AddPrinterDriver</strong></a> function installs a local or remote printer driver and associates the configuration, data, and driver files.<br /> For more flexibility in installing or upgrading printer drivers, use the <a href="addprinterdriverex.md"><strong>AddPrinterDriverEx</strong></a> function because it allows strict upgrade, strict downgrade, copying of newer files only, and copying of all files (regardless of the file time stamps).<br /><blockquote>[!Note]<br />Installing a printer driver without a driver package is no longer recommended. Use <a href="installprinterdriverfrompackage.md"><strong>InstallPrinterDriverFromPackage</strong></a> instead.</blockquote><br /> | 
-| <a href="addprinterdriverex.md"><strong>AddPrinterDriverEx</strong></a><br /> | The <a href="/windows/desktop/printdocs/addprinterdriverex"><strong>AddPrinterDriverEx</strong></a> function installs a local or remote printer driver and links the configuration, data, and driver files. Besides having the capabilities of <a href="addprinterdriver.md"><strong>AddPrinterDriver</strong></a>, it also has options that permit strict upgrade, strict downgrade, copying of newer files only, and copying of all files (regardless of file time stamps).<br /><blockquote>[!Note]<br />Installing a printer driver without a driver package is no longer recommended. Use <a href="installprinterdriverfrompackage.md"><strong>InstallPrinterDriverFromPackage</strong></a> instead.</blockquote><br /> | 
+| [**AddPrinterDriver**](addprinterdriver.md)<br> | The [**AddPrinterDriver**](/windows/desktop/printdocs/addprinterdriver) function installs a local or remote printer driver and associates the configuration, data, and driver files.<br> For more flexibility in installing or upgrading printer drivers, use the [**AddPrinterDriverEx**](addprinterdriverex.md) function because it allows strict upgrade, strict downgrade, copying of newer files only, and copying of all files (regardless of the file time stamps).<br> **Note:** Installing a printer driver without a driver package is no longer recommended. Use [**InstallPrinterDriverFromPackage**](installprinterdriverfrompackage.md) instead.<br> | 
+| [**AddPrinterDriverEx**](addprinterdriverex.md)<br> | The [**AddPrinterDriverEx**](/windows/desktop/printdocs/addprinterdriverex) function installs a local or remote printer driver and links the configuration, data, and driver files. Besides having the capabilities of [**AddPrinterDriver**](addprinterdriver.md), it also has options that permit strict upgrade, strict downgrade, copying of newer files only, and copying of all files (regardless of file time stamps).<br> **Note:** Installing a printer driver without a driver package is no longer recommended. Use [**InstallPrinterDriverFromPackage**](installprinterdriverfrompackage.md) instead.<br> | 
 | <a href="addprintprocessor.md"><strong>AddPrintProcessor</strong></a><br /> | The <a href="/windows/desktop/printdocs/addprintprocessor"><strong>AddPrintProcessor</strong></a> function installs a print processor on the specified server and adds the print-processor name to the list of supported print processors.<br /> | 
 | <a href="addprintprovidor.md"><strong>AddPrintProvidor</strong></a><br /> | The <a href="/windows/desktop/printdocs/addprintprovidor"><strong>AddPrintProvidor</strong></a> function installs a local print provider and links the configuration, data, and provider files.<br /> | 
 | <a href="coreprinterdriverinstalled.md"><strong>CorePrinterDriverInstalled</strong></a><br /> | The <a href="/windows/desktop/printdocs/coreprinterdriverinstalled"><strong>CorePrinterDriverInstalled</strong></a> function reports whether a core printer driver with a specified GUID, date, and version is installed.<br /> | 

desktop-src/printdocs/xps-document-errors.md

@@ -33,7 +33,7 @@ The following table lists all the **HRESULT** values that can be returned by the
 | <span id="XPS_E_INVALID_FONT_URI"></span><span id="xps_e_invalid_font_uri"></span><dl><dt><strong>XPS_E_INVALID_FONT_URI</strong></dt><dt>0x8052000a</dt></dl> | The font URI is not valid, possibly because it contains an empty fragment or characters that are not valid.<br /> | 
 | <span id="XPS_E_INVALID_LANGUAGE"></span><span id="xps_e_invalid_language"></span><dl><dt><strong>XPS_E_INVALID_LANGUAGE</strong></dt><dt>0x80520000</dt></dl> | The specified language is either not valid or not correctly formatted.<br /> | 
 | <span id="XPS_E_INVALID_LOOKUP_TYPE"></span><span id="xps_e_invalid_lookup_type"></span><dl><dt><strong>XPS_E_INVALID_LOOKUP_TYPE</strong></dt><dt>0x80520006</dt></dl> | The lookup key name references an object that is not the correct type for the call; for example, if the method returns a brush but the lookup key name refers to a geometry object.<br /> | 
-| <span id="XPS_E_INVALID_MARKUP"></span><span id="xps_e_invalid_markup"></span><dl><dt><strong>XPS_E_INVALID_MARKUP</strong></dt><dt>0x8052000c</dt></dl> | The markup being read contains an element or an attribute that does not conform to the <a href="https://www.ecma-international.org/activities/XML%20Paper%20Specification/XPS%20Standard%20WD%201.6.pdf">XML Paper Specification</a>.<br /><blockquote>[!Note]<br />To represent floating-point values, the XPS OM uses the <strong>FLOAT</strong> data type instead of <strong>DOUBLE</strong>. If an XPS document has an element with floating-point data that does not fit into a <strong>FLOAT</strong> value, this error will be returned when that value is encountered during deserialization.</blockquote><br /><br /> | 
+| **XPS_E_INVALID_MARKUP**<br>0x8052000c<br> | The markup being read contains an element or an attribute that does not conform to the [XML Paper Specification](https://www.ecma-international.org/activities/XML%20Paper%20Specification/XPS%20Standard%20WD%201.6.pdf).<br> **Note:** To represent floating-point values, the XPS OM uses the **FLOAT** data type instead of **DOUBLE**. If an XPS document has an element with floating-point data that does not fit into a **FLOAT** value, this error will be returned when that value is encountered during deserialization.<br> | 
 | <span id="XPS_E_INVALID_NAME"></span><span id="xps_e_invalid_name"></span><dl><dt><strong>XPS_E_INVALID_NAME</strong></dt><dt>0x80520001</dt></dl> | The string that was passed is not a valid name, according to the XML Paper Specification. <br /> | 
 | <span id="XPS_E_INVALID_OBFUSCATED_FONT_URI"></span><span id="xps_e_invalid_obfuscated_font_uri"></span><dl><dt><strong>XPS_E_INVALID_OBFUSCATED_FONT_URI</strong></dt><dt>0x8052000f</dt></dl> | Reserved.<br /> | 
 | <span id="XPS_E_INVALID_PAGE_SIZE"></span><span id="xps_e_invalid_page_size"></span><dl><dt><strong>XPS_E_INVALID_PAGE_SIZE</strong></dt><dt>0x80520003</dt></dl> | The page dimensions contain a page size value that is not valid. <br /> |