From 50f6532955bfd86e11cef78b955d500afce98008 Mon Sep 17 00:00:00 2001
From: Jen Kuntz <44136928+jenkuntz@users.noreply.github.com>
Date: Mon, 8 Dec 2025 10:39:59 -0500
Subject: [PATCH] Update this-document-has-been-posted.md

The "it should read XYZ" in step 7 all contained a decimal point that would not be in the literal results expected in SQL. Moved the period to outside of the quoted expected result.
---
 support/dynamics/gp/this-document-has-been-posted.md | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)

diff --git a/support/dynamics/gp/this-document-has-been-posted.md b/support/dynamics/gp/this-document-has-been-posted.md
index 152a3b59bb8..347a2a53cf7 100644
--- a/support/dynamics/gp/this-document-has-been-posted.md
+++ b/support/dynamics/gp/this-document-has-been-posted.md
@@ -62,9 +62,9 @@ To resolve this problem, use an SQL query tool to discover why the document is d
    > The Dex_Row_ID value.
 7. Check values in the following columns for the SOP Document. If any of these values are incorrect, the document may appear as posted.
 
-    PSTGSTUS (For an unposted document, it should read "0.")  
-    BCHSOURC (For an unposted document, it should read "Sales Entry.")  
-    VOIDSTTS (For an unposted document, it should read "0.")  
+    PSTGSTUS (For an unposted document, it should read "0".)  
+    BCHSOURC (For an unposted document, it should read "Sales Entry".)  
+    VOIDSTTS (For an unposted document, it should read "0".)  
     TRXSORCE (For an unposted document, it should be blank.)
 8. Run the following scripts against the company database to correct any of the four values from step 6: