• Section headings and variables should follow the case conventions displayed in this guide. (For example, "[SECURITYMANAGER–PrivApp]", not "[securitymanager–privapp]"; and "PrivBitsTotal", not "privbitstotal", or "PRIVBITSTOTAL".) These case conventions help to clearly distinguish variable names making them easier to read; and
• Variables and their values should follow the spacing conventions displayed in this guide. For example, separate all variables from the equals sign using a tab, and separate the equals sign from the value using a tab. Again, this helps to clearly distinguish and organize variables and values, making them easier to read.
Note: Throughout this section, the documented variables requiring a value of 1 (true) or 0 (false) will also accept and recognize the literal values TRUE or FALSE; however, for the purposes of consistency, those variables requiring a true or false value will appear with 1 and 0 rather than TRUE or FALSE in this guide.
Now that you are familiar with the structure of the configuration files, their section headings and their variables, we will look at the process involved in editing a configuration file.