slightly modified documentation for CETCOMPAT flag based on recent implementation of IDE flag

Laxman Sole · Laxman Sole · commit dc46dc6bb91e · 2020-06-03T11:29:46.000-07:00
diff --git a/docs/build/reference/cetcompat.md b/docs/build/reference/cetcompat.md
@@ -33,7 +33,7 @@ The **/CETCOMPAT** option is available beginning in the Visual Studio 2019 Previ
 
 1. Select the **CET Shadow Stack Compatible** property.
 
-1. In the dropdown control, choose **Yes(/CETCOMPAT)** to enable EH continuation metadata, or **No(/CETCOMPAT:NO)** to disable it.
+1. In the dropdown control, choose **Yes (/CETCOMPAT)** to enable EH continuation metadata, or **No (/CETCOMPAT:NO)** to disable it.
 
 
 ### To set this linker option programmatically
diff --git a/docs/build/reference/guard-enable-eh-continuation-metadata.md b/docs/build/reference/guard-enable-eh-continuation-metadata.md
@@ -34,7 +34,7 @@ Code compiled by using **/guard:ehcont** can be linked to libraries and object f
 
 The linker will fatal, because it cannot generate metadata in these scenarios, which means throwing an exception will likely crash at runtime.
 
-For SEH section info that is in comdats but not compiled with /guard:ehcont, the linker will emit a warning, but will generate correct but conservative metadata for the section. To ignore warnings, open project's **property pages->Configuration Properties->Linker->Advanced-> Ignore Warning LNK4291(EHCont metadata)**
+For SEH section info that is in comdats but not compiled with /guard:ehcont, the linker will emit a warning **LNK4291**. In this case linker will generate correct but conservative metadata for the section. To ignore this warning, use [/IGNORE (Ignore Specific Warnings)](ignore-ignore-specific-warnings.md).
 
 
 To check if a binary contains EHCONT data, look for the following when dumping the binary's load config:
