[DOCS] Update vamc-facilities.md to move full width banner content.

This content was moved into a content model document so there would be one source of truth.

READMES/vamc-facilities.md

@@ -32,13 +32,7 @@ Vaccines but is expandable to handle more or eventually all services.
 
 ## System Banner Alerts and Situation Updates to GovDelivery
 
-When a system creates a system banner alert (node: full_width_banner_alert) or an accompanying situation update (paragraph: situation_update), they have an option to send a notification through GovDelivery Bulletins (A gov specific mail service.)  However since there is a delay between when one is published and when it actually hits the website, it was a business requirement that the bulletin not go out before the actual content landed on the VA.gov. To make sure that content stays in sync, we queue all the items that are supposed to go to GovDelivery along with the timestamp of when each one was queued. The content build records the timestamp from when they make the graphQL query, and when the FE build is complete and the new content is out, the last thing in the build step is to ping an endpoint (/api/govdelivery_bulletins/queue?EndTime=[unix timestamp]) in the CMS with the timestamp from the query, at which point the CMS processes all the items in the queue from *before* that timestamp.
-
-The handling is performed in:
-  * custom module [VA Gov GovDelivery](https://github.com/department-of-veterans-affairs/va.gov-cms/tree/main/docroot/modules/custom/va_gov_govdelivery)
-  * which leverages contrib [GovDelivery Bulletins](https://www.drupal.org/project/govdelivery_bulletins)
-
-  The queue and related settings can be seen here [/admin/config/services/govdelivery-bulletins](https://prod.cms.va.gov/admin/config/services/govdelivery-bulletins)
+Information related to this can be found in CMS Content Model Document for [Full Width Banner alerts with Situation Updates](https://prod.cms.va.gov/admin/structure/types/manage/full_width_banner_alert/document)
 
 ----