Imported Upstream version 2.0.0.11353upstream/2.0.0.11353

2 files changed, 2 insertions, 2 deletions

diff --git a/Documentation/coding-guidelines/EventLogging.md b/Documentation/coding-guidelines/EventLogging.md
index a53d6e9844..8ba84d7001 100644
--- a/Documentation/coding-guidelines/EventLogging.md
+++ b/Documentation/coding-guidelines/EventLogging.md
@@ -1,6 +1,6 @@
 # CoreClr Event Logging Design
 
-##Introduction
+## Introduction
 
 Event Logging is a mechanism by which CoreClr can provide a variety of information on it's state. This Logging works by inserting explicit logging calls by the developer within the VM . The Event Logging mechanism is largely based on [ETW- Event Tracing For Windows](https://msdn.microsoft.com/en-us/library/windows/desktop/bb968803(v=vs.85).aspx)
 
diff --git a/Documentation/coding-guidelines/cross-platform-performance-and-eventing.md b/Documentation/coding-guidelines/cross-platform-performance-and-eventing.md
index f332724478..37a3135f93 100644
--- a/Documentation/coding-guidelines/cross-platform-performance-and-eventing.md
+++ b/Documentation/coding-guidelines/cross-platform-performance-and-eventing.md
@@ -1,6 +1,6 @@
 # .NET Cross-Plat Performance and Eventing Design
 
-##Introduction
+## Introduction
 
 As we bring up CoreCLR on the Linux and OS X platforms, it’s important that we determine how we’ll measure and analyze performance on these platforms.  On Windows we use an event based model that depends on ETW, and we have a good amount of tooling that builds on this approach.  Ideally, we can extend this model to Linux and OS X and re-use much of the Windows tooling.