diff --git a/docs/framework/setting.md b/docs/framework/setting.md
index 3ca89908f525509b6697d54376ad8deda3ad8353..c2045f17f0bc6da179a5d782bf3c4061e902088c 100644
--- a/docs/framework/setting.md
+++ b/docs/framework/setting.md
@@ -151,7 +151,7 @@ As with core settings, all settings declared in extensions should have appropria
 
 1. Provide that the settings folder is declared [Multisite extension example](https://github.com/eileenmcnaughton/org.civicrm.multisite/blob/master/multisite.php#L347).
 2. Declare settings as in the same standard as CiviCRM Core [Multisite extension example](https://github.com/eileenmcnaughton/org.civicrm.multisite/blob/master/settings/Multisite.setting.php).
-3. Create Settings form, a [good example of generic metadata based setings form in an extension](https://github.com/eileenmcnaughton/nz.co.fuzion.civixero/blob/master/CRM/Civixero/Form/XeroSettings.php) - note that only the setting filter is non-generic
+3. Create Settings form, a [good example of generic metadata based settings form in an extension](https://github.com/eileenmcnaughton/nz.co.fuzion.civixero/blob/master/CRM/Civixero/Form/XeroSettings.php) - note that only the setting filter is non-generic
 4. Use `cv api system.flush` or `Admin → System Settings → Cleanup Caches` to flush CiviCRM caches and register your new settings metadata.
 
 ## Adding Setting Config to Admin Forms.