Skip to content

Commit 44de556

Browse files
committed
Simplify terminology for docs build system
1 parent 1d377fa commit 44de556

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

reference/docs-conceptual/community/contributing/general-markdown.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -1,17 +1,17 @@
11
---
22
description: This article provides specific guidance for using Markdown in our documentation.
3-
ms.date: 03/30/2025
3+
ms.date: 04/29/2025
44
title: Markdown best practices
55
---
66
# Markdown best practices
77

88
This article provides specific guidance for using Markdown in our documentation. It isn't a tutorial
99
for Markdown. If you need a tutorial for Markdown, see this [Markdown cheatsheet][12].
1010

11-
The Microsoft Open Publishing System (OPS) that builds our documentation uses [markdig][06] to
12-
process the Markdown documents. Markdig parses the documents based on the rules of the latest
13-
[CommonMark][10] specification. OPS follows the CommonMark specification and adds some extensions
14-
for platform-specific features, such as tables and alerts.
11+
The build pipeline that builds our documentation uses [markdig][06] to process the Markdown
12+
documents. Markdig parses the documents based on the rules of the latest [CommonMark][10]
13+
specification. OPS follows the CommonMark specification and adds some extensions for
14+
platform-specific features, such as tables and alerts.
1515

1616
The CommonMark specification is stricter about the construction of some Markdown elements. Pay close
1717
attention to the details provided in this document.

0 commit comments

Comments
 (0)