diff --git a/_kbarticles/2021-05-24-secureauth-issues.md b/_kbarticles/2021-05-24-secureauth-issues.md
index 73f3811d3..a40d60e42 100644
--- a/_kbarticles/2021-05-24-secureauth-issues.md
+++ b/_kbarticles/2021-05-24-secureauth-issues.md
@@ -5,23 +5,16 @@ date: May 20, 2021
 excerpt: If you see an error while logging into cloud.gov, these tips can help you troubleshoot
 ---
 
-## If you are using GSA's single sign on integration (SecureAuth)
+## If you are using your agency's single sign on integration
 
-When logging in to cloud.gov, you may encounter an error message that includes reference to `InResponseToField`. For example, something like:
-
-```
-InResponseToField of the Response doesn’t correspond to sent message {code}
-```
-
-This is typically caused by SecureAuth having an old certificate or session cookie in your browser, and is not related to the cloud.gov platform. 
-
-Things you can check:
+Check the following:
 
 * You can verify this issue is affecting your login by opening a private or incognito session in your browser and retry logging in. 
 
 * You can try clearing all cache and cookies, restart your browser, and retry logging in.
 
-If these steps don't work, [GSA also has a tool that can clear these items](https://secureauth.gsa.gov/secureauth2/cleancert.aspx). Note - if you are a Mac user, this site will only work in Safari.
+If these steps don't work, and your agency identity provider works for other 
+services, open an issue with [support@cloud.gov].
 
 ## If you are using the cloud.gov identity provider (IDP)
 
diff --git a/_posts/2025-01-02-v2api-deprecation.md b/_posts/2025-01-02-v2api-deprecation.md
index 3f524f439..a39d4eb88 100644
--- a/_posts/2025-01-02-v2api-deprecation.md
+++ b/_posts/2025-01-02-v2api-deprecation.md
@@ -1,7 +1,7 @@
 ---
 layout: post
 date: "2025-01-07"
-title: "Deprecation CloudFoundry API v2"
+title: "End-of-life for CloudFoundry API v2"
 excerpt: "You may need to update versions of the CF CLI, terraform, and some other tools to support v3"
 ---