From d8fef721a07870dc2dd6d86cd2063ea1b3e2a491 Mon Sep 17 00:00:00 2001
From: Andrew Morgan <1342360+anoadragon453@users.noreply.github.com>
Date: Tue, 25 Mar 2025 10:35:01 +0000
Subject: [PATCH] Correct typo "SAML" -> SSO in mapping providers docs (#18276)

---
 changelog.d/18276.doc         | 1 +
 docs/sso_mapping_providers.md | 2 +-
 2 files changed, 2 insertions(+), 1 deletion(-)
 create mode 100644 changelog.d/18276.doc

diff --git a/changelog.d/18276.doc b/changelog.d/18276.doc
new file mode 100644
index 0000000000..cacf6daf76
--- /dev/null
+++ b/changelog.d/18276.doc
@@ -0,0 +1 @@
+Correct a small typo in the SSO mapping providers documentation.
\ No newline at end of file
diff --git a/docs/sso_mapping_providers.md b/docs/sso_mapping_providers.md
index d6c4e860ae..4d33c8da75 100644
--- a/docs/sso_mapping_providers.md
+++ b/docs/sso_mapping_providers.md
@@ -10,7 +10,7 @@ As an example, a SSO service may return the email address
 to turn that into a displayname when creating a Matrix user for this individual.
 It may choose `John Smith`, or `Smith, John [Example.com]` or any number of
 variations. As each Synapse configuration may want something different, this is
-where SAML mapping providers come into play.
+where SSO mapping providers come into play.
 
 SSO mapping providers are currently supported for OpenID and SAML SSO
 configurations. Please see the details below for how to implement your own.