dotnet · janvorli · Feb 18, 2015 · Feb 12, 2015 · Feb 13, 2015 · Feb 13, 2015
diff --git a/Documentation/clr-code-guide.md b/Documentation/clr-code-guide.md
@@ -1,5 +1,12 @@
-What Every CLR Developer Must Know Before Writing Code
-===
+What Every CLR Developer Must Know Before Writing Code
+=== 
+
+Written in 2006, by:
+
+- Rick Byers ([@RByers](https://github.com/RByers))
+- Jan Kotas ([@jkotas](https://github.com/jkotas))
+- Mike Stall ([@mikestall](https://github.com/mikestall))
+- Rudi Martin ([@Rudi-Martin](https://github.com/Rudi-Martin))
 
 # Why you must read this document
 

diff --git a/Documentation/glossary.md b/Documentation/glossary.md
@@ -6,6 +6,7 @@ This glossary defines terms, both common and more niche, that are important to u
 As much as possible, we should link to the most authoritative and recent source of information for a term. That approach should be the most helpful for people who want to learn more about a topic.
 
 * CLR: Common Language Runtime
+* COMPLUS: An early name for the .NET platform, back when it was envisioned as a successor to the COM platform (hence, "COM+"). Used in various places in the CLR infrastructure, most prominently as a common prefix for the names of internal configuration settings. Note that this is different from the product that eventually ended up being named [COM+](https://msdn.microsoft.com/en-us/library/windows/desktop/ms685978.aspx).
 * COR: [Common Object Runtime](http://www.danielmoth.com/Blog/mscorlibdll.aspx). The name of .NET before it was named .NET.
 * DAC: Data Access Component. An abstraction layer over the internal structures in the runtime.
 * EE: Execution Engine.
@@ -14,4 +15,4 @@ As much as possible, we should link to the most authoritative and recent source
 * SVR: The CLR used to be built as two variants, with one called "mscorsvr.dll", to mean the "server" version. In particular, it contained the server GC implementation, which was intended for multi-threaded apps capable of taking advantage of multiple processors. In the .NET Framework 2 release, the two variants were merged into "mscorwks.dll". The WKS version was the default, however the SVR version remained available.
 * URT: Universal Runtime. Ancient name for what ended up being .NET, is used in the WinError facility name FACILITY_URT.
 * VM: Virtual machine.
-* WKS: The CLR used to be built as two variants, with one called "mscorwks.dll", to mean the "workstation" version. In particular, it contained the client GC implementation, which was intended for single-threaded apps, independent of how many processors were on the machine. In the .NET Framework 2 release, the two variants were merged into "mscorwks.dll". The WKS version was the default, however the SVR version remained available.
+* WKS: The CLR used to be built as two variants, with one called "mscorwks.dll", to mean the "workstation" version. In particular, it contained the client GC implementation, which was intended for single-threaded apps, independent of how many processors were on the machine. In the .NET Framework 2 release, the two variants were merged into "mscorwks.dll". The WKS version was the default, however the SVR version remained available.
diff --git a/Documentation/images/type-system-dependencies.png b/Documentation/images/type-system-dependencies.png
diff --git a/Documentation/images/typeloader-fig1.png b/Documentation/images/typeloader-fig1.png
diff --git a/Documentation/images/typeloader-fig2.png b/Documentation/images/typeloader-fig2.png
diff --git a/Documentation/images/typeloader-fig3.png b/Documentation/images/typeloader-fig3.png
diff --git a/Documentation/images/typeloader-fig4.png b/Documentation/images/typeloader-fig4.png
diff --git a/Documentation/index.md b/Documentation/index.md
@@ -7,6 +7,7 @@ This repo includes several documents that explain both high-level and low-level
 
 - [Introduction to the Common Language Runtime](intro-to-clr.md)
 - [Mscorlib and Calling Into the Runtime](mscorlib.md)
+- [Type Loader](type-loader.md)
 - [Stack Walking](stackwalking.md)
 - [Book of the Runtime FAQ](botr-faq.md)
 
@@ -23,7 +24,7 @@ This repo includes several documents that explain both high-level and low-level
 
 - [MSDN Entry for the CLR](http://msdn.microsoft.com/en-us/library/8bs2ecf4(VS.71).aspx)
 - [Wikipedia Entry for the CLR](http://en.wikipedia.org/wiki/Common_Language_Runtime)
-- [ECMA Standard for the Common Language Infrastructure (CLI)](http://msdn.microsoft.com/en-us/netframework/aa569283.aspx)
+- [ECMA Standard for the Common Language Infrastructure (CLI)](http://www.ecma-international.org/publications/standards/Ecma-335.htm)
   - [Partition I Concepts and Architecture](http://download.microsoft.com/download/7/3/3/733AD403-90B2-4064-A81E-01035A7FE13C/MS%20Partition%20I.pdf)
   - [Partition II Meta Data Definition and Semantics](http://download.microsoft.com/download/7/3/3/733AD403-90B2-4064-A81E-01035A7FE13C/MS%20Partition%20II.pdf)
   - [Partition III CIL Instruction Set](http://download.microsoft.com/download/7/3/3/733AD403-90B2-4064-A81E-01035A7FE13C/MS%20Partition%20III.pdf)

diff --git a/Documentation/intro-to-clr.md b/Documentation/intro-to-clr.md
@@ -251,13 +251,13 @@ Phew!  The runtime does a lot! It has taken many pages just to describe _some_ o
 
 - [MSDN Entry for the CLR][clr]
 - [Wikipedia Entry for the CLR](http://en.wikipedia.org/wiki/Common_Language_Runtime)
-- [ECMA Standard for the Common Language Infrastructure (CLI)](http://msdn.microsoft.com/en-us/netframework/aa569283.aspx)
+- [ECMA Standard for the Common Language Infrastructure (CLI)][ecma-spec]
   - [Partition I Concepts and Architecture](http://download.microsoft.com/download/7/3/3/733AD403-90B2-4064-A81E-01035A7FE13C/MS%20Partition%20I.pdf)
   - [Partition II Meta Data Definition and Semantics](http://download.microsoft.com/download/7/3/3/733AD403-90B2-4064-A81E-01035A7FE13C/MS%20Partition%20II.pdf)
   - [Partition III CIL Instruction Set][cil-spec]
 - [.NET Framework Design Guidelines](http://msdn.microsoft.com/en-us/library/ms229042.aspx)
 
-[ecma-spec]: http://msdn.microsoft.com/en-us/netframework/aa569283.aspx
+[ecma-spec]: http://www.ecma-international.org/publications/standards/Ecma-335.htm
 [clr]: http://msdn.microsoft.com/en-us/library/8bs2ecf4(VS.71).aspx
 [cil-spec]: http://download.microsoft.com/download/7/3/3/733AD403-90B2-4064-A81E-01035A7FE13C/MS%20Partition%20III.pdf
 [fx-design-guidelines]: http://msdn.microsoft.com/en-us/library/ms229042.aspx
diff --git a/Documentation/mscorlib.md b/Documentation/mscorlib.md
@@ -85,7 +85,7 @@ Do not replicate the comments into your actual QCall implementation. This is for
 	    // All QCalls should have the following DllImport and
 	    // SuppressUnmanagedCodeSecurity attributes
 	    [DllImport(JitHelpers.QCall, CharSet = CharSet.Unicode)]
-	    SuppressUnmanagedCodeSecurity]
+	    [SuppressUnmanagedCodeSecurity]
 	    // QCalls should always be static extern.
 	    private static extern bool Bar(int flags, string inString, StringHandleOnStack retString);