Add yaml front matter to all asciidoc files

[web.git] / docs / uci.txt

diff --git a/docs/uci.txt b/docs/uci.txt
index 98b88865c9723906f5a2df5567aa8d572d2e1d6c..0d9048eedd2a0ec0db275d759781addee25c1f96 100644 (file)
--- a/docs/uci.txt
+++ b/docs/uci.txt
@@ -1,3 +1,5 @@
+---
+---
 The UCI Configuration System
 ============================
 
@@ -5,7 +7,7 @@ include::menu.inc[]
 
 == UCI - Unified Configuration Interface
 
-_LEDE_ uses UCI to store its configuration. This is a human readable file format using typed and named section. Each section contains a number of options. Options can be single values or list of values. All configuration files are stored in the /etc/config/ folder. You can manually edit these files.
+_LEDE_ uses UCI to store its configuration. This is a human readable file format using typed and named sections. Each section contains a number of options. Options can be single values or lists of values. All configuration files are stored in the /etc/config/ folder. You can manually edit these files.
 
 ----
 root@lede:/# cat etc/config/system
@@ -22,7 +24,7 @@ config timeserver ntp
        option enable_server 0
 ----
 
-Alternatively you may use the uci CLI to read/modify their content. Using the CLI has the advantage that you do not need to worry about the validity of the syntax. Some user do however prefer to make changes manually, they should however be aware that even minor syntax errors will make the whole file unparsable and not just the specific section and/or option that was modified.
+Alternatively you may use the uci CLI to read/modify their content. Using the CLI has the advantage that you do not need to worry about the validity of the syntax. Some users do however prefer to make changes manually, they should be aware that even minor syntax errors will make the whole file unparsable and not just the specific section and/or option that was modified.
 
 ----
 root@lede:/# uci show system
@@ -35,21 +37,13 @@ system.ntp.enabled='1'
 system.ntp.enable_server='0'
 ----
 
-When using the CLI to modify values, you will find that all changes first get staged and not commited to the file directly. If you want to permanently store changes you need to commit them. After calling the commit command, you can also make the system reload and apply the changes that you made
+When using the CLI to modify values, you will find that all changes first get staged and not commited to the file directly. If you want to permanently store changes you need to commit them. After calling the commit command, you can also make the system reload and apply the changes that you made.  (This will only affect services that correctly use link:procd.html[procd] init scripts)
 
 ----
 root@lede:/# uci set system.@system[0].hostname=foo
 root@lede:/# uci commit
 root@lede:/# reload_config
 root@lede:/#
-root@foo:/#
 ----
 
-=== UCI files
 
-* link:uci_dnsmasq.html[/etc/config/dhcp]
-* link:uci_dropbear.html[/etc/config/dropbear]
-* link:uci_firewall.html[/etc/config/firewall]
-* link:uci_net.html[/etc/config/network]
-* link:uci_qos.html[/etc/config/qos]
-* link:uci_system.html[/etc/config/system]