Merge pull request #3745 from manu-silicon/docs

Ensure proper spelling of COMPlus_xxx environment variables

2 files changed, 5 insertions, 5 deletions

diff --git a/src/debug/daccess/daccess.cpp b/src/debug/daccess/daccess.cpp
index 9e20926863..2465c62cef 100644
--- a/src/debug/daccess/daccess.cpp
+++ b/src/debug/daccess/daccess.cpp
@@ -3198,7 +3198,7 @@ ClrDataAccess::ClrDataAccess(ICorDebugDataTarget * pTarget, ICLRDataTarget * pLe
 
     // Verification asserts are disabled by default because some debuggers (cdb/windbg) probe likely locations
     // for DAC and having this assert pop up all the time can be annoying.  We let derived classes enable 
-    // this if they want.  It can also be overridden at run-time with COMPLUS_DbgDACAssertOnMismatch,
+    // this if they want.  It can also be overridden at run-time with COMPlus_DbgDACAssertOnMismatch,
     // see ClrDataAccess::VerifyDlls for details.
     m_fEnableDllVerificationAsserts = false;
 #endif
@@ -6974,7 +6974,7 @@ void ClrDataAccess::SetTargetConsistencyChecks(bool fEnableAsserts)
 // Notes:
 //     The implementation of ASSERT accesses this via code:DacTargetConsistencyAssertsEnabled
 //     
-//     By default, this is disabled, unless COMPLUS_DbgDACEnableAssert is set (see code:ClrDataAccess::ClrDataAccess).
+//     By default, this is disabled, unless COMPlus_DbgDACEnableAssert is set (see code:ClrDataAccess::ClrDataAccess).
 //     This is necessary for compatibility.  For example, SOS expects to be able to scan for
 //     valid MethodTables etc. (which may cause ASSERTs), and also doesn't want ASSERTs when working
 //     with targets with corrupted memory.
@@ -7073,7 +7073,7 @@ HRESULT ClrDataAccess::VerifyDlls()
 
 #ifdef _DEBUG
         // Check if verbose asserts are enabled.  The default is up to the specific instantiation of
-        // ClrDataAccess, but can be overridden (in either direction) by a COMPLUS knob.
+        // ClrDataAccess, but can be overridden (in either direction) by a COMPlus_ knob.
         // Note that we check this knob every time because it may be handy to turn it on in 
         // the environment mid-flight.
         DWORD dwAssertDefault = m_fEnableDllVerificationAsserts ? 1 : 0;
@@ -7105,7 +7105,7 @@ HRESULT ClrDataAccess::VerifyDlls()
                 "Actual %s timestamp: %s\n"\
                 "DAC will now fail to initialize with a CORDBG_E_MISMATCHED_CORWKS_AND_DACWKS_DLLS\n"\
                 "error.  If you really want to try and use the mimatched DLLs, you can disable this\n"\
-                "check by setting COMPLUS_DbgDACSkipVerifyDlls=1.  However, using a mismatched DAC\n"\
+                "check by setting COMPlus_DbgDACSkipVerifyDlls=1.  However, using a mismatched DAC\n"\
                 "DLL will usually result in arbitrary debugger failures.\n",
                 MAIN_CLR_DLL_NAME_A,
                 MAIN_CLR_DLL_NAME_A,
diff --git a/src/debug/di/process.cpp b/src/debug/di/process.cpp
index a6ff19a170..a2bf15d849 100644
--- a/src/debug/di/process.cpp
+++ b/src/debug/di/process.cpp
@@ -976,7 +976,7 @@ CordbProcess::CordbProcess(ULONG64 clrInstanceId,
     // On Debug builds, we'll ASSERT by default whenever the target appears to be corrupt or 
     // otherwise inconsistent (both in DAC and DBI).  But we also need the ability to 
     // explicitly test corrupt targets.
-    // Tests should set COMPLUS_DbgIgnoreInconsistentTarget=1 to suppress these asserts
+    // Tests should set COMPlus_DbgIgnoreInconsistentTarget=1 to suppress these asserts
     // Note that this controls two things:
     //     1) DAC behavior - see code:IDacDbiInterface::DacSetTargetConsistencyChecks
     //     2) RS-only consistency asserts - see code:CordbProcess::TargetConsistencyCheck