From fd8a0659ada7eb1f81d6d6ba175d74512b41d59f Mon Sep 17 00:00:00 2001 From: Patrick Vacek Date: Mon, 12 Aug 2019 17:15:08 +0200 Subject: Fix some minor typos. Signed-off-by: Patrick Vacek --- docs/modules/ROOT/pages/provisioning-methods.adoc | 4 ++-- docs/modules/ROOT/pages/supported-boards.adoc | 6 +++--- 2 files changed, 5 insertions(+), 5 deletions(-) diff --git a/docs/modules/ROOT/pages/provisioning-methods.adoc b/docs/modules/ROOT/pages/provisioning-methods.adoc index c376c78..0f9051e 100644 --- a/docs/modules/ROOT/pages/provisioning-methods.adoc +++ b/docs/modules/ROOT/pages/provisioning-methods.adoc @@ -1,4 +1,4 @@ -= Manual provisoning += Manual provisioning //MC: TOMERGE: Looks mostly like a duplicate of this topic: https://github.com/advancedtelematic/aktualizr/blob/master/docs/ota-client-guide/modules/ROOT/pages/simulate-device-cred-provtest.adoc @@ -19,4 +19,4 @@ For more extensive information on provisioning methods, see the following topics //MC: Web links because this topic is only viewable in Github * link:https://docs.ota.here.com/ota-client/dev/client-provisioning-methods.html[Device provisioning methods] -* link:https://docs.ota.here.com/ota-client/dev/enable-device-cred-provisioning.html[Enable device-credential provisioning and install device certificates] \ No newline at end of file +* link:https://docs.ota.here.com/ota-client/dev/enable-device-cred-provisioning.html[Enable device-credential provisioning and install device certificates] diff --git a/docs/modules/ROOT/pages/supported-boards.adoc b/docs/modules/ROOT/pages/supported-boards.adoc index c3b29bf..3c7e3f9 100644 --- a/docs/modules/ROOT/pages/supported-boards.adoc +++ b/docs/modules/ROOT/pages/supported-boards.adoc @@ -23,7 +23,7 @@ If your board isn't supported yet, you can add board integration code yourself. Take a look at the https://github.com/advancedtelematic/meta-updater-minnowboard[Minnowboard] or https://github.com/advancedtelematic/meta-updater-raspberrypi[Raspberry Pi] integration layers for examples. -If you want our developers to add support for your board, contact us at mailto:otaconnect.support@here.com[] and we can discuss a potential NRE (Non-recurring Engineering) aggreement. +If you want our developers to add support for your board, contact us at mailto:otaconnect.support@here.com[] and we can discuss a potential NRE (Non-recurring Engineering) agreement. [NOTE] ==== @@ -34,7 +34,7 @@ Your images will also need network connectivity to be able to reach an actual OT == Minimum hardware requirements for controllers (ECUs) -The aktuallizr binary is a lightweight {cpp} application between 2-5 MB in size. It uses a miniumum about of resources when idle. +The aktualizr binary is a lightweight {cpp} application between 2-5 MB in size. It uses a minimum amount of resources when idle. The following hardware is required for your primary ECU: @@ -44,4 +44,4 @@ The following hardware is required for your primary ECU: [NOTE] ==== If you plan to send updates to secondary, low-performance ECUs, you can also use a more minimal implementaton called link:https://github.com/advancedtelematic/aktualizr/tree/master/partial/libuptiny[`libuptiny`]. This utility is only 10 KB and performs a minimal verification of software metadata that is less resource intensive. For more information on `libuptiny`, contact us at mailto:otaconnect.support@here.com[]. -==== \ No newline at end of file +==== -- cgit v1.2.3-54-g00ecf