Merge pull request #3429 from department-of-veterans-affairs/db/fix-a…

…lert-example-include-paths Fix include paths
department-of-veterans-affairs · Oct 24, 2024 · e1be2cf · e1be2cf
2 parents 0e93d7d + 211261f
commit e1be2cf
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/src/_components/alert/alert-sign-in.md b/src/_components/alert/alert-sign-in.md
@@ -19,7 +19,7 @@ anchors:
 ---
 
 ## Examples
-{% include content/file-upload.md %}
+{% include content/sign-in-alert-examples.md %}
 
 ## Usage
 

diff --git a/src/_patterns/help-users-to/sign-in.md b/src/_patterns/help-users-to/sign-in.md
@@ -42,7 +42,7 @@ This pattern works differently depending on the product and the account type a p
 2. Implement both of the yellow verification alerts. If a person signs in with an unverified account, they should encounter 1 of the 2 variations. One is for unverified **Login.gov** and **ID.me** accounts, and one is for unverified **My HealtheVet** accounts.
   **Note:** This pattern is currently tailored to products that require verified (LOA3 or IAL2) accounts. If your product accepts unverified (LOA1 or IAL1) accounts, you'll need to adjust the content in the blue sign-in alert. And you won't need to implement the yellow verification alerts. Work with CAIA and the identity team to adjust for your situation.
 
-{% include content/file-sign-in-alert-examples.md %}
+{% include content/sign-in-alert-examples.md %}
 
 **All teams should take these steps when using this pattern:**