Add disclaimer to Language Specification pages

Author: sdwheeler

reference/docs-conceptual/lang-spec/chapter-01.md

@@ -1,23 +1,11 @@
 ---
 description: This Language Specification describe the syntax, semantics, and behavior of the PowerShell language.
-ms.date: 05/19/2021
+ms.date: 01/08/2025
 title: Windows PowerShell Language Specification 3.0
 ---
 # Windows PowerShell Language Specification 3.0
 
-The _Windows PowerShell Language Specification 3.0_ was published in December 2012 and is based on
-PowerShell 3.0. The specification document is available as a Microsoft Word document from the
-Microsoft Download Center at:
-[https://www.microsoft.com/download/details.aspx?id=36389](https://www.microsoft.com/download/details.aspx?id=36389)
-
-That Word document has been converted for presentation here on Microsoft Learn. During conversion,
-some editorial changes have been made to accommodate formatting for the Docs platform. Some typos
-and minor errors have been corrected.
-
-> [!IMPORTANT]
-> The contents of this documentation may not reflect the current state of PowerShell in its current
-> version. There is no plan to update this documentation to reflect the current state. This
-> documentation is presented here for historical reference.
+[!INCLUDE [Disclaimer](../../includes/language-spec.md)]
 
 ## 1. Introduction
 

reference/docs-conceptual/lang-spec/chapter-02.md

@@ -5,6 +5,8 @@ title: Lexical structure
 ---
 # 2. Lexical Structure
 
+[!INCLUDE [Disclaimer](../../includes/language-spec.md)]
+
 ## 2.1 Grammars
 
 This specification shows the syntax of the PowerShell language using two grammars. The _lexical

reference/docs-conceptual/lang-spec/chapter-03.md

@@ -5,6 +5,8 @@ title: Basic concepts
 ---
 # 3. Basic concepts
 
+[!INCLUDE [Disclaimer](../../includes/language-spec.md)]
+
 ## 3.1 Providers and drives
 
 A *provider* allows access to data and components that would not otherwise be easily accessible at

reference/docs-conceptual/lang-spec/chapter-04.md

@@ -5,14 +5,16 @@ title: Types
 ---
 # 4. Types
 
-In PowerShell, each value has a type, and types fall into one of two main categories: **value types**
-and **reference types**. Consider the type `int`, which is typical of value types. A value of type
-`int` is completely self-contained; all the bits needed to represent that value are stored in that
-value, and every bit pattern in that value represents a valid value for its type. Now, consider the
-array type `int[]`, which is typical of reference types. A so-called value of an array type can hold
-either a reference to an object that actually contains the array elements, or the **null reference**
-whose value is `$null`. The important distinction between the two type categories is best
-demonstrated by the differences in their semantics during assignment. For example,
+[!INCLUDE [Disclaimer](../../includes/language-spec.md)]
+
+In PowerShell, each value has a type, and types fall into one of two main categories: **value
+types** and **reference types**. Consider the type `int`, which is typical of value types. A value
+of type `int` is completely self-contained; all the bits needed to represent that value are stored
+in that value, and every bit pattern in that value represents a valid value for its type. Now,
+consider the array type `int[]`, which is typical of reference types. A so-called value of an array
+type can hold either a reference to an object that actually contains the array elements, or the
+**null reference** whose value is `$null`. The important distinction between the two type categories
+is best demonstrated by the differences in their semantics during assignment. For example,
 
 ```powershell
 $i = 100 # $i designates an int value 100

reference/docs-conceptual/lang-spec/chapter-05.md

@@ -5,6 +5,8 @@ title: Variables
 ---
 # 5. Variables
 
+[!INCLUDE [Disclaimer](../../includes/language-spec.md)]
+
 A variable represents a storage location for a value, and that value has a type. Traditional
 procedural programming languages are statically typed; that is, the runtime type of a variable is
 that with which it was declared at compile time. Object-oriented languages add the idea of

reference/docs-conceptual/lang-spec/chapter-06.md

@@ -5,6 +5,8 @@ title: Conversions
 ---
 # 6. Conversions
 
+[!INCLUDE [Disclaimer](../../includes/language-spec.md)]
+
 A *type conversion* is performed when a value of one type is used in a context that requires a
 different type. If such a conversion happens automatically it is known as *implicit conversion*. (A
 common example of this is with some operators that need to convert one or more of the values

reference/docs-conceptual/lang-spec/chapter-07.md

@@ -5,6 +5,8 @@ title: Expressions
 ---
 # 7. Expressions
 
+[!INCLUDE [Disclaimer](../../includes/language-spec.md)]
+
 Syntax:
 
 ```Syntax

reference/docs-conceptual/lang-spec/chapter-08.md

@@ -5,6 +5,8 @@ title: Statements
 ---
 # 8. Statements
 
+[!INCLUDE [Disclaimer](../../includes/language-spec.md)]
+
 ## 8.1 Statement blocks and lists
 
 Syntax:

reference/docs-conceptual/lang-spec/chapter-09.md

@@ -5,6 +5,8 @@ title: Arrays
 ---
 # 9. Arrays
 
+[!INCLUDE [Disclaimer](../../includes/language-spec.md)]
+
 ## 9.1 Introduction
 
 PowerShell supports arrays of one or more dimensions with each dimension having zero or more

reference/docs-conceptual/lang-spec/chapter-10.md

@@ -5,6 +5,8 @@ title: Hashtables
 ---
 # 10. Hashtables
 
+[!INCLUDE [Disclaimer](../../includes/language-spec.md)]
+
 Syntax:
 
 > [!TIP]