ATLAS-2303: updated Area 0 models in line with the latest wiki

Signed-off-by: Madhan Neethiraj <madhan@apache.org>
diff --git a/addons/models/0000-Area0/0025-Locations_model.json b/addons/models/0000-Area0/0025-Locations_model.json
index 5dbfd9b..878de35 100644
--- a/addons/models/0000-Area0/0025-Locations_model.json
+++ b/addons/models/0000-Area0/0025-Locations_model.json
@@ -3,8 +3,8 @@
   "structDefs": [],
   "classificationDefs": [
     {
-      "name": "PhysicalLocation",
-      "description":"Physical Location means that the location represents a physical place where, for example, Hosts, Servers and hence data may be located. This could be an area of a data center, the building the data center is located in, or even the country where the server/data is located.",
+      "name": "FixedLocation",
+      "description":"FixedLocation means that the location represents a physical place where, for example, Hosts, Servers and hence data may be located. This could be an area of a data center, the building the data center is located in, or even the country where the server/data is located.",
       "superTypes": [],
       "entityTypes":["Location"],
       "typeVersion": "1.0",
@@ -36,8 +36,8 @@
       "attributeDefs": []
     },
     {
-      "name": "MobileLocation",
-      "description":"Mobile Location means that the Host is mobile. An example of such a host would be a smart phone or IoT (Internet of Things) enabled vehicle.",
+      "name": "CyberLocation",
+      "description":"CyberLocation means that the location describes something in cyber space.",
       "superTypes": [],
       "entityTypes":["Location"],
       "typeVersion": "1.0",
@@ -56,7 +56,7 @@
   "entityDefs": [
     {
       "name": "Location",
-      "description":"The location can be used to define country, data centers, geographic locations. The granularity in which locations are modeled depends on the organisation. It is important to understand where assets are located to ensure they are properly protected and comply with data sovereignty laws. The notion of a location is variable and the classifications PhysicalLocation, SecureLocation and MobileLocation help to clarify the nature of the location.",
+      "description":"The location can be used to define country, data centers, geographic locations. The granularity in which locations are modeled depends on the organisation. It is important to understand where assets are located to ensure they are properly protected and comply with data sovereignty laws. The notion of a location is variable and the classifications FixedLocation, SecureLocation and CyberLocation help to clarify the nature of the location.",
       "superTypes": [
         "Referenceable"
       ],
diff --git a/addons/models/0000-Area0/0030-HostsAndPlatforms_model.json b/addons/models/0000-Area0/0030-HostsAndPlatforms_model.json
index a3fd721..18b1039 100644
--- a/addons/models/0000-Area0/0030-HostsAndPlatforms_model.json
+++ b/addons/models/0000-Area0/0030-HostsAndPlatforms_model.json
@@ -21,7 +21,7 @@
   "entityDefs": [
     {
       "name": "Host",
-      "description":"",
+      "description":"A Host is an IT Infrastructure concept associated with the hardware running the systems. It provides a mechanism for describing a unit of hardware that provides the ability to host software servers.",
       "superTypes": [
         "Infrastructure"
       ],
diff --git a/addons/models/0000-Area0/0035-ComplexHosts_model.json b/addons/models/0000-Area0/0035-ComplexHosts_model.json
index 4effe2b..dda8e75 100644
--- a/addons/models/0000-Area0/0035-ComplexHosts_model.json
+++ b/addons/models/0000-Area0/0035-ComplexHosts_model.json
@@ -15,7 +15,7 @@
     },
     {
       "name": "Virtualcontainer",
-      "description":"A Virtual Container or a Server Container, provides the services of a host to the servers deployed on it. Docker is an example of a virtual container. When the server makes requests for storage, network access etc, the VirtualContainer delegates the requests to the equivalent services of the actual host it is deployed on. VirtualContainers can be hosted on other VirtualContainers, but to actually run they need to ultimately be deployed on to a real physical Host.",
+      "description":"A Virtual Container or a Server Container, provides the services of a host to the software servers deployed on it. Docker is an example of a virtual container. When the server makes requests for storage, network access etc, the VirtualContainer delegates the requests to the equivalent services of the actual host it is deployed on. VirtualContainers can be hosted on other VirtualContainers, but to actually run they need to ultimately be deployed on to a real physical Host.",
       "superTypes": [
         "Host"
       ],
diff --git a/addons/models/0000-Area0/0040-Servers_model.json b/addons/models/0000-Area0/0040-Servers_model.json
index 83d2800..fa505be 100644
--- a/addons/models/0000-Area0/0040-Servers_model.json
+++ b/addons/models/0000-Area0/0040-Servers_model.json
@@ -20,7 +20,7 @@
   "entityDefs": [
     {
       "name": "Server",
-      "description": "Servers describe the middleware servers (such as application servers, data movement engines and database servers) that run on the Hosts. Within the Server model, we capture its userid. Most metadata repositories are run in a secure mode requiring incoming requests to incluye the requester's security credentials. Therefore we have an identifier for each unique logged on security identity (aka userId). This identity is recorded within specific entities and relationships when they are created or updated. By storing the user identifier for the server, it is possible to correlate the server with the changes to the metadata (and related data assets) that it makes.",
+      "description": "Software Servers describe the middleware software servers (such as application servers, data movement engines and database servers) that run on the Hosts. Within the Software Server model, we capture the userid that it runs under. Most metadata repositories are run in a secure mode requiring incoming requests to incluye the requester's security credentials. Therefore we have an identifier for each unique logged on security identity (aka userId). This identity is recorded within specific entities and relationships when they are created or updated. By storing the user identifier for the server, it is possible to correlate the server with the changes to the metadata (and related data assets) that it makes.",
       "superTypes": [
         "Infrastructure"
       ],