From d9aea91651f13590b5fb15a0b8d84e4c25376097 Mon Sep 17 00:00:00 2001
From: James Newton-King <james@newtonking.com>
Date: Sat, 8 Sep 2012 01:37:12 -0700
Subject: [PATCH] -Documentation

---
 Doc/ReducingSerializedJSONSize.aml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/Doc/ReducingSerializedJSONSize.aml b/Doc/ReducingSerializedJSONSize.aml
index 7a996448..247c98ac 100644
--- a/Doc/ReducingSerializedJSONSize.aml
+++ b/Doc/ReducingSerializedJSONSize.aml
@@ -39,7 +39,7 @@
         The way to tackle this scenario is to add the
         <codeEntityReference>T:System.Runtime.Serialization.DataContractAttribute</codeEntityReference>
         to the class and
-        <codeEntityReference>T:System.Runtime.Serialization.DataMemberAttributes</codeEntityReference>
+        <codeEntityReference>T:System.Runtime.Serialization.DataMemberAttribute</codeEntityReference>
         to the properties to serialize. This is opt-in
         serialization, only the properties you mark up with be serialized, compared to
         opt-out serialization using JsonIgnoreAttribute.</para>