fixed typo and indents in conformance topic (MicrosoftDocs#267)

mikeblome · Colin Robertson · commit 3742c161f06a · 2017-05-11T11:09:25.000-07:00
diff --git a/docs/cpp-conformance-improvements-2017.md b/docs/cpp-conformance-improvements-2017.md
@@ -355,12 +355,12 @@ In previous versions of Visual Studio, the compiler in some cases would fail to
 ```cpp
 template<typename T> 
 struct S { 
-template<typename U> static int f() = delete; 
+   template<typename U> static int f() = delete; 
 }; 
  
 void g() 
 { 
-decltype(S<int>::f<int>()) i; // this should fail 
+   decltype(S<int>::f<int>()) i; // this should fail 
 }
 ```
 To fix the error, declare i as `int`.
@@ -385,16 +385,16 @@ Now the compiler will emit a warning if it can know at compile time that a nativ
 class A 
 { 
 public: 
-A() : p_(new int) {} 
-~A() { delete p_; } 
+   A() : p_(new int) {} 
+   ~A() { delete p_; } 
  
-A(A const &) = delete; 
-A(A &&rhs) { 
-p_ = rhs.p_; 
+   A(A const &) = delete; 
+   A(A &&rhs) { 
+   p_ = rhs.p_; 
 } 
  
 private: 
-int *p_; 
+   int *p_; 
 }; 
  
 #pragma unmanaged 
@@ -559,7 +559,7 @@ void h()
    g(42); 
 }
 ```
-### Unitialized const variables
+### Uninitialized const variables
 Visual Studio 2017 RTW release had a regression in which the C++ compiler would not issue a diagnostic if a 'const' variable was not initialized. This regression has been fixed in Visual Studio 2017 Update 1. The following code now produces "warning C4132: 'Value': const object should be initialized":
 
 ```cpp
