From 0411bfded2ee9aefb8178a47d139b54913490d5b Mon Sep 17 00:00:00 2001
From: Doug Rohrer <doug@therohrers.org>
Date: Wed, 5 Oct 2016 11:05:44 -0400
Subject: Update per review comments.

---
 system/doc/reference_manual/typespec.xml | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

(limited to 'system/doc/reference_manual/typespec.xml')

diff --git a/system/doc/reference_manual/typespec.xml b/system/doc/reference_manual/typespec.xml
index 4421529dda..ced584ed35 100644
--- a/system/doc/reference_manual/typespec.xml
+++ b/system/doc/reference_manual/typespec.xml
@@ -411,8 +411,8 @@
       This is checked by the compiler and results in a compilation error
       if a violation is detected. 
     </p>
-    <warning>
-      <p>In previous (pre-19) versions of Erlang, for fields without initial values,
+    <note>
+      <p>Before Erlang/OTP 19, for fields without initial values,
       the singleton type <c>'undefined'</c> was added to all declared types.
       In other words, the following two record declarations had identical 
       effects:</p>
@@ -428,7 +428,7 @@
       This is no longer the case. If you require <c>'undefined'</c> in your record field
       type, you must explicitly add it to the typespec, as in the 2nd example.
     </p>
-    </warning>
+    </note>
     <p>
       Any record, containing type information or not, once defined, 
       can be used as a type using the following syntax:
-- 
cgit v1.2.3