From e412d551f348034e82f2389c2f61d651637e8f37 Mon Sep 17 00:00:00 2001
From: Victor Lin <13424970+victorlin@users.noreply.github.com>
Date: Wed, 11 Dec 2024 16:46:32 -0800
Subject: [PATCH] =?UTF-8?q?=F0=9F=9A=A7=20reword=20interoperability=20intr?=
 =?UTF-8?q?o=20sentence?=
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

---
 static-site/content/blog/2024-12-10-auspice-2024.md | 7 +++----
 1 file changed, 3 insertions(+), 4 deletions(-)

diff --git a/static-site/content/blog/2024-12-10-auspice-2024.md b/static-site/content/blog/2024-12-10-auspice-2024.md
index 8503c8c28..1ad098863 100644
--- a/static-site/content/blog/2024-12-10-auspice-2024.md
+++ b/static-site/content/blog/2024-12-10-auspice-2024.md
@@ -46,10 +46,9 @@ for early clades in the tree such as 20I (Alpha).
 
 ## View in Other Platforms
 
-Interoperability between platforms is something we've been big proponents of,
-and are part of [PH4GE](https://pha4ge.org/) to help support this. For many
-years, Nextstrain.org has supported [fetching](https://nextstrain.org/fetch)
-HTTPS-addressable Auspice JSONs.
+Historically, we have always been strong advocates for interoperability between
+platforms. For many years, Nextstrain.org has supported
+[fetching](https://nextstrain.org/fetch) HTTPS-addressable Auspice JSONs.
 [UShER](https://genome.ucsc.edu/cgi-bin/hgPhyloPlace) uses this feature to link
 to Auspice views for subtrees.