Many typo fixes and some rewording (opnsense#80)

Author: MichaelDeciso

LICENSE

@@ -38,8 +38,8 @@ Some pictures are licensed under the Creative Commons Zero (CC0) license:
 
 https://creativecommons.org/publicdomain/zero/1.0/
 
-# Logo's
-Logo's may be subject to additional copyrights, property
+# Logos
+Logos may be subject to additional copyrights, property
 rights, trademarks etc. and may require the consent of a third party or the
 license of these rights. Deciso B.V. does not represent or make any warranties
 that it owns or licenses any of the mentioned, nor does it grant them.

README.md

@@ -22,7 +22,7 @@ Some pictures are licensed under the Creative Commons Zero (CC0) license:
 
 https://creativecommons.org/publicdomain/zero/1.0/
 
-Logo's may be subject to additional copyrights, property 
+Logos may be subject to additional copyrights, property 
 rights, trademarks etc. and may require the consent of a third party or the
 license of these rights. Deciso B.V. does not represent or make any warranties
 that it owns or licenses any of the mentioned, nor does it grant them.

source/develop.rst

@@ -7,7 +7,7 @@ Development Manual
 The OPNsense® project invites developers to start developing with OPNsense:
 "For your own purpose or even better to join us in creating the best FreeBSD
 based open source firewall available!" The development workflow & build process
-has been redesigned to make it more straightforward and easy for developers to
+have been redesigned to make it more straightforward and easy for developers to
 build OPNsense.
 
 Being able to get the sources and build it yourself is one of the key factors of

source/development/architecture.rst

@@ -81,7 +81,7 @@ first layer initializes Phalcon’s routing, which handles requests and
 delivers them to the controller based on its url. User content is
 generated using Volt templates, which are picked by the controller.
 Because Phalcon’s default Models function with (relational) databases
-and we are using xml data, our model implementation is custom. But
+and we are using XML data, our model implementation is custom. But
 wherever possible we use components from Phalcon (for example,
 validation is handled using Phalcon’s classes). For a detailed
 description on the routing principles used in OPNsense, visit Frontend
@@ -98,7 +98,7 @@ controllers, with the use of views, can be found at :doc:`/development/frontend/
 Models
 ------
 
-All models are defined by a combination of a class and an xml containing
+All models are defined by a combination of a class and an XML containing
 a (nested) definition. More information on defining models can be found
 at the frontend model page :doc:`/development/frontend/models`.
 

source/development/components/acl.rst

@@ -45,7 +45,7 @@ Using the system from php is rather simple:
 Usage in Volt templates
 -----------------------
 
-The acl scheme is bound to the default UI controller, and can be used by
+The ACL scheme is bound to the default UI controller, and can be used by
 using the acl keyword:
 
 .. code-block:: jinja

source/development/components/menusystem.rst

@@ -37,8 +37,8 @@ An example of how to create a menu, is given below:
     // test, print menu as structured named array
     print_r($menu->getItems("/testpage.php"));
 
-The current version only implements a static menu defined by one xml file
-(models/OPNsense/Base/Menu/Menu.xml), but extending with additional xml files
+The current version only implements a static menu defined by one XML file
+(models/OPNsense/Base/Menu/Menu.xml), but extending with additional XML files
 is already supported in the component for future use.
 
 --------

source/development/examples/helloworld.rst

@@ -120,7 +120,7 @@ Not all modules contain additional code in the php class, sometimes all
 the standard behaviour is already sufficient for your
 modules/application.
 
-Which is the model xml template, our skeleton starts with something like
+Which is the model XML template, our skeleton starts with something like
 this:
 
 .. code-block:: xml
@@ -266,9 +266,9 @@ Adding Fields
 .. rubric:: Adding fields to your model
    :name: adding-fields-to-your-model
 
-When building the skeleton, we have created an empty model (xml), which
+When building the skeleton, we have created an empty model (XML), which
 we are going to fill with some attributes now. The items section of the
-model xml should contain the structure you want to use for your
+model XML should contain the structure you want to use for your
 application, you can create trees to hold data in here. All leaves
 should contain a field type to identify and validate it’s content. The
 list of attributes for our application can be translated to this:
@@ -310,12 +310,12 @@ Enabled).
 Presentation XML
 ----------------
 
-.. rubric:: Create a presentation xml to feed your template
+.. rubric:: Create a presentation XML to feed your template
    :name: create-a-presentation-xml-to-feed-your-template
 
 Because creating forms is one of the key assets of the system, we have
 build some easy to use wrappers to guide you through the process. First
-we create an xml file for the presentation, which defines fields to use
+we create an XML file for the presentation, which defines fields to use
 and adds some information for your template to render. Create a file in
 your controller directory using the sub directory forms and name it
 general.xml. Next copy in the following content:
@@ -392,7 +392,7 @@ Create API calls
    :name: create-api-calls-to-retrieve-and-store-data
 
 The framework provides some helpful utilities to get and set data from
-and to the configuration xml by using your defined model. First step in
+and to the configuration XML by using your defined model. First step in
 binding your model to the system is to add a method to the
 SettingsController to fetch the data from our configuration (or provide
 the defaults if there is no content).
@@ -530,7 +530,7 @@ Let’s give it a try and save our data, without modifying it first.
 
 Next correct the errors and save again, on successful save the data
 should be stored in the config.xml. If you want to change validation
-messages, just edit the model xml and add your message in the
+messages, just edit the model XML and add your message in the
 ValidationMessage tag. For example:
 
 .. code-block:: xml
@@ -848,15 +848,15 @@ automatically picks up this new information.
 Plugin to access control (ACL)
 ------------------------------
 
-If we want to authorize users to access this module, we can add an acl
+If we want to authorize users to access this module, we can add an ACL
 to this module. Without it, only admin users can access it. Create an
-xml file in the model directory name ACL/ACL.xml and place the following
+XML file in the model directory name ACL/ACL.xml and place the following
 content in it:
 
 .. code-block:: xml
 
     <acl>
-        <!-- unique acl key, must be globally unique for all acl's  -->
+        <!-- unique acl key, must be globally unique for all ACLs  -->
         <page-user-helloworld>
             <name>WebCfg - Users: Hello World! </name>
             <description>Allow access to the Hello World! module</description>
@@ -867,7 +867,7 @@ content in it:
         </page-user-helloworld>
     </acl>
 
-This creates an acl key named “page-user-helloworld” which authorizes
+This creates an ACL key named “page-user-helloworld” which authorizes
 access to both the ui and API urls of this application. You can now
 grant access to this module from the system user manager.
 

source/development/frontend/models.rst

@@ -4,7 +4,7 @@ Creating Models
 
 A model represents the data which the application will use and takes
 care of the interaction to that data. In OPNsense most of the relevant
-data is physically stored in an xml structure (config.xml). The primary
+data is physically stored in an XML structure (config.xml). The primary
 goal for OPNsense models is to structure the use of configuration data,
 by creating a clear abstraction layer.
 
@@ -44,7 +44,7 @@ When you design a model, the next thing to do is to figure out what data is
 relevant for your application or module and think of the rules it should comply
 to (for example, if you need an email address you might want to validate the
 input). Designing the actual model is as simple as creating an xml file and
-putting in your structure, the name of our xml file should be the same as the
+putting in your structure, the name of our XML file should be the same as the
 base name of our model suffixed by .xml.
 
 Using the same model, we would create the following file:
@@ -91,7 +91,7 @@ Now let's explain what's happing here one tag at a time.
 The content of a items tag describes the full tree based structure which holds
 our data, in theory this could be as large as you want it to be, but keep in
 mind that the content for your model should be logical and understandable. Every
-node in the tree could have a type, which defines it's behavior, nodes without a
+node in the tree could have a type, which defines its behavior, nodes without a
 type are just containers.
 
 From top to bottom we find the following nodes in our tree:

source/development/guidelines/basics.rst

@@ -78,7 +78,7 @@ implementation is one example of this stage.
 
 **3)** Moving on
 (re)build new parts, using our new modules, which provide a layered development
-system to automatically support API calls from other systems and xml based model
+system to automatically support API calls from other systems and XML based model
 templates to describe configuration data.
 
 *See also:*

source/development/how-tos/api.rst

@@ -41,7 +41,7 @@ Code sample (python)
 --------------------
 
 For the python code sample we use the nice "requests" library
-(http://docs.python-requests.org/en/latest/), which makes http calls
+(http://docs.python-requests.org/en/latest/), which makes HTTP calls
 very easy.
 
 Before you can start, make sure your OPNsense has a valid SSL
@@ -102,7 +102,7 @@ Using curl
 ----------
 
 Simple testing with curl is also possible, the sample below uses the
-same credentials, but ignores the ssl certificate check (-k) for
+same credentials, but ignores the SSL certificate check (-k) for
 testing.
 
 .. code-block:: sh