diff --git a/articles/getting_to_know/whatis/content_pipeline/CP_Architecture.md b/articles/getting_to_know/whatis/content_pipeline/CP_Architecture.md
index 64b92f47..f82c0642 100644
--- a/articles/getting_to_know/whatis/content_pipeline/CP_Architecture.md
+++ b/articles/getting_to_know/whatis/content_pipeline/CP_Architecture.md
@@ -40,6 +40,8 @@ The managed code objects created by the Content Processor are serialized into a
 
 The format of data in the .XNB file is tightly coupled to the MonoGame Framework. It is not designed for use by other runtime libraries.
 
+If you are intested in the format of the .XNB files you can view the [XNB specification](XNB Format.docx).
+
 ### Runtime Components
 
 Runtime components of the Content Pipeline support loading and using the transformed game asset by your MonoGame game. These components use the [MonoGame library](../monogame_class_library/index.md), which can be extended to create custom components.
diff --git a/articles/getting_to_know/whatis/content_pipeline/XNB Format.docx b/articles/getting_to_know/whatis/content_pipeline/XNB Format.docx
new file mode 100644
index 00000000..f8a5c45e
Binary files /dev/null and b/articles/getting_to_know/whatis/content_pipeline/XNB Format.docx differ
diff --git a/ci.docfx.json b/ci.docfx.json
index 6f8a5604..06e09547 100644
--- a/ci.docfx.json
+++ b/ci.docfx.json
@@ -54,6 +54,7 @@
           "**/videos/**",
           "**/files/**",
           "**/snippets/**",
+          "**/*.docx",
           "CNAME"
         ]
       }
diff --git a/docfx.json b/docfx.json
index 21d73ce0..ed8f0d3a 100644
--- a/docfx.json
+++ b/docfx.json
@@ -54,6 +54,7 @@
           "**/videos/**",
           "**/files/**",
           "**/snippets/**",
+          "**/*.docx",
           "CNAME"
         ]
       }