'\_' (underscore).
Version values are dot separated fields MAJOR.MINOR.REVISION.
-Such version would preferabily follow guidelines of
-[semantic versionning][semantic-version].
+Such version would preferably follow guidelines of
+[semantic versioning][semantic-version].
### The element content
The element *content* is mandatory (for version 2.x, blowfish) and must designate a file
-(subject to localisation) with its attribute *src*.
+(subject to localization) with its attribute *src*.
The content designed depends on its type. See below for the known types.
- declare the expected permissions
- declare the exported apis
-The specification of [widgets][widgets] is intentded to describe
+The specification of [widgets][widgets] is intended to describe
only one application. In the present case, we expect to describe
more than just an application. For example, a publisher could
provide a widget containing a service, an application for tuning
- link:
- The framework connect in memory by dinamically linking
+ The framework connect in memory by dynamically linking
- cloud: [PROPOSAL - NOT IMPLEMENTED]
of the installed widgets.
This configuration file named `afm-unit.conf` installed
-on the system wiht the path `/etc/afm/afm-unit.conf`
+on the system with the path `/etc/afm/afm-unit.conf`
describes how to generate all units from the *config.xml*
configuration files of widgets. The description uses an extended
version of the templating formalism of [mustache][]
of the config files of widgets.
In a second step, the mustache template `afm-unit.conf`
-is instanciated using the C library [mustach][] that follows
+is instantiated using the C library [mustach][] that follows
the rules of [mustache][mustache] and with all its available
extensions:
- use of colon (:) for explicit substitution
- test of values with = or =!
-In a third step, the result of instanciating `afm-unit.conf`
-for the widget is splited in units. To achieve that goal,
+In a third step, the result of instantiating `afm-unit.conf`
+for the widget is split in units. To achieve that goal,
the lines containing specific directives are searched.
Any directive occupy one full line. The directives are:
[app-manifest]: http://www.w3.org/TR/appmanifest "Web App Manifest"
[tizen-security]: https://wiki.tizen.org/wiki/Security "Tizen security home page"
[tizen-secu-3]: https://wiki.tizen.org/wiki/Security/Tizen_3.X_Overview "Tizen 3 security overview"
-[semantic-version]: http://semver.org/ "Semantic versionning"
+[semantic-version]: http://semver.org/ "Semantic versioning"