aboutsummaryrefslogtreecommitdiff
path: root/src/backends/README.md
diff options
context:
space:
mode:
authorMatteo Martincigh <matteo.martincigh@arm.com>2019-09-18 12:01:49 +0100
committerÁron Virginás-Tar <aron.virginas-tar@arm.com>2019-09-18 14:50:16 +0000
commit0bd586ceb2a1e3f8132d009cf48dc46c76ae09e4 (patch)
treeeb1ec98f229319cfc64374cd98a905700f50e0da /src/backends/README.md
parentbab9dc64cb4fad9cc0c4d48678f3e7f841b6504d (diff)
downloadarmnn-0bd586ceb2a1e3f8132d009cf48dc46c76ae09e4.tar.gz
CONSERV-3867 Fix typos in the Dynamic Backends readme file
Change-Id: I73253cf1bee6a626ec65ab92555f70fbf00d98fc Signed-off-by: Matteo Martincigh <matteo.martincigh@arm.com>
Diffstat (limited to 'src/backends/README.md')
-rw-r--r--src/backends/README.md6
1 files changed, 3 insertions, 3 deletions
diff --git a/src/backends/README.md b/src/backends/README.md
index 96ffd77603..a75bc9cb28 100644
--- a/src/backends/README.md
+++ b/src/backends/README.md
@@ -298,9 +298,9 @@ Only one path is allowed for the override via the CreationOptions class.
By setting the value of the ```m_DynamicBackendsPath``` to a path in the filesystem, Arm NN will entirely ignore the list of paths passed via the
```DYNAMIC_BACKEND_PATHS``` compiler directive.
-All the specified paths are validate before processing (they must exist, must be directories, and must be absolute paths),
+All the specified paths are validated before processing (they must exist, must be directories, and must be absolute paths),
in case of error a warning message will be added to the log, but Arm NN's execution will not be stopped.
-If all path are not valid, then no dynamic backends will be loaded in the Arm NN's runtime.
+If all paths are not valid, then no dynamic backends will be loaded in the Arm NN's runtime.
Passing an empty list of paths at compile-time and providing no path override at runtime will effectively disable the
dynamic backend loading feature, and no dynamic backends will be loaded into Arm NN's runtime.
@@ -316,7 +316,7 @@ Arm NN will try to load only the files that match the following accepted naming
Only alphanumeric characters are allowed for both the `<vendor>` and the `<name>` fields, namely lowercase and/or uppercase characters,
and/or numerical digits (see the table below for examples).
-Only dots and numbers are allow for the optional `<version>` field.
+Only dots and numbers are allowed for the optional `<version>` field.
Symlinks to other files are allowed to support the standard linux shared object versioning: