From b17b330aaca9f68a653a7223ec0d35365339d293 Mon Sep 17 00:00:00 2001
From: eileen <emcnaughton@wikimedia.org>
Date: Fri, 10 Jan 2020 14:05:28 +1300
Subject: [PATCH] Increment suggested version to reflect info.xml

Arguably afform still works on older versions but breaking changes have happened & if people
use it on older you want a buyer-beware type feeling
---
 README.md     | 2 +-
 docs/embed.md | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 4f9201b..97e890a 100644
--- a/README.md
+++ b/README.md
@@ -22,7 +22,7 @@ if you already have a basic understanding of CiviCRM API and AngularJS.  It is l
 ## Requirements
 
 * PHP v7.0+
-* CiviCRM v5.7+
+* CiviCRM v5.22+
 
 <!--
 ## Installation (Web UI)
diff --git a/docs/embed.md b/docs/embed.md
index 58698f7..3e291da 100644
--- a/docs/embed.md
+++ b/docs/embed.md
@@ -73,4 +73,4 @@ cv open 'civicrm/contact?cid=100'
 
 What does this buy us?  It means that a downstream admin (using APIs/GUIs) can fork `ang/myContactName.aff.html` --
 but all the other components can cleanly track the canonical release. This significantly reduces the costs and risks
-of manging upgrades and changes.
+of managing upgrades and changes.
-- 
GitLab