From f44a28affea5841186250b66fd5ce72a8afbe349 Mon Sep 17 00:00:00 2001 From: José Bollo Date: Tue, 24 Jul 2018 11:53:44 +0200 Subject: Tiny documentation fixes MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Some english improvement of the documentation. Change-Id: I066c41d657a1921ed7dcc46dafcc7c65d122239c Signed-off-by: José Bollo --- docs/afb-migration-to-binding-v3.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'docs/afb-migration-to-binding-v3.md') diff --git a/docs/afb-migration-to-binding-v3.md b/docs/afb-migration-to-binding-v3.md index 266a8b0c..f7e09fd9 100644 --- a/docs/afb-migration-to-binding-v3.md +++ b/docs/afb-migration-to-binding-v3.md @@ -6,12 +6,12 @@ for the following reasons: - integration of the security requirements within the bindings - simplification of the API (after developer feedbacks) -- removal of obscure features, cleanup +- removal of obscure features and cleanup The ***binder*** can run ***bindings*** v1, v2 and/or v3 in any combination. Thus moving from v1 or v2 to v3 is not enforced at this time. But ... -In the face to face meeting of Karlsruhe it was decided to remove support +In the face to face meeting in Karlsruhe it was decided to remove support of bindings v1 and to deprecate the use of bindings v2. So at the end, **IT IS HIGHLY NEEDED TO SWITCH TO VERSION 3** @@ -19,7 +19,7 @@ So at the end, **IT IS HIGHLY NEEDED TO SWITCH TO VERSION 3** This guide covers the migration of bindings from version 2 to version 3. The migration from version 1 is not treated here because bindings version 1 -are very old and probably does not exist anymore. If needed you can refer +are very old and probably do not exist anymore. If needed you can refer to the old [guide to migrate bindings from v1 to v2](legacy/afb-migration-v1-to-v2.html). -- cgit 1.2.3-korg