chore(manifest): Re-create description fields in manifest to use Noun Phrase Style

Author: m8rmclaren

docs/gcploadbal.md

@@ -173,8 +173,8 @@ The following table describes the required and optional fields for the `GCPLoadB
 | --------- | ----------- | ------------------------- |
 | Category | Select "GCP Load Balancer" or the customized certificate store name from the previous step. | |
 | Container | Optional container to associate certificate store with. | |
-| Client Machine | For the Client Machine field, enter the name or IP address of the Orchestrator server that will handle the jobs for the GCP Load Balancer. For example, you might enter 'orchestrator.example.local' or '192.168.0.1'. | |
-| Store Path | For the Store Path field, enter your Google Cloud project ID. Optionally, you can append a region to the project ID, separated by a '/', to specify a particular region. For example, 'my-gcp-project' or 'my-gcp-project/us-central1'. | |
+| Client Machine | The name or IP address of the Orchestrator server that will handle GCP jobs. Example: orchestrator-server.example.com or 192.168.1.100. | |
+| Store Path | The Google Cloud project ID, optionally appended with the region code if targeting a specific region. Example: my-project-id or my-project-id/us-central1. | |
 | Orchestrator | Select an approved orchestrator capable of managing `GCPLoadBal` certificates. Specifically, one with the `GCPLoadBal` capability. | |
 
 * **Using kfutil**

integration-manifest.json

@@ -1,36 +1,18 @@
 {
-    "$schema": "/Users/hroszell/coding/dev/staff-tools/keyfactor.github.io/v2/integration-manifest-schema.json",
+    "$schema": "https://keyfactor.github.io/v2/integration-manifest-schema.json",
     "integration_type": "orchestrator",
     "name": "GCP Load Balancer",
     "status": "production",
     "update_catalog": true,
     "link_github": true,
     "support_level": "kf-supported",
     "release_dir": "GCPLoadBalancer/bin/Release/netcoreapp3.1",
-    "description": "The Google Cloud Platform (GCP) Load Balancer Orchestrator allows for the management of Google Cloud Platform Load Balancer certificate stores.  Inventory, Management-Add, and Management-Remove functions are supported.  Also, re-binding to endpoints IS supported for certificate renewals (but NOT adding new certificates).  The orchestrator uses the Google Cloud Compute Engine API (https://cloud.google.com/compute/docs/reference/rest/v1) to manage stores.",
+    "description": "The GCP Load Balancer Universal Orchestrator extension enables the remote management of SSL certificates on Google Cloud Load Balancers through Keyfactor Command.",
     "about": {
         "orchestrator": {
             "UOFramework": "10.1",
             "keyfactor_platform_version": "9.10",
             "pam_support": false,
-            "win": {
-                "supportsCreateStore": false,
-                "supportsDiscovery": false,
-                "supportsManagementAdd": true,
-                "supportsManagementRemove": true,
-                "supportsReenrollment": false,
-                "supportsInventory": true,
-                "platformSupport": "Unused"
-            },
-            "linux": {
-                "supportsCreateStore": false,
-                "supportsDiscovery": false,
-                "supportsManagementAdd": false,
-                "supportsManagementRemove": false,
-                "supportsReenrollment": false,
-                "supportsInventory": false,
-                "platformSupport": "Unused"
-            },
             "store_types": [
                 {
                     "Name": "GCP Load Balancer",
@@ -55,8 +37,8 @@
                     },
                     "Properties": [],
                     "EntryParameters": [],
-                    "ClientMachineDescription": "For the Client Machine field, enter the name or IP address of the Orchestrator server that will handle the jobs for the GCP Load Balancer. For example, you might enter 'orchestrator.example.local' or '192.168.0.1'.",
-                    "StorePathDescription": "For the Store Path field, enter your Google Cloud project ID. Optionally, you can append a region to the project ID, separated by a '/', to specify a particular region. For example, 'my-gcp-project' or 'my-gcp-project/us-central1'."
+                    "ClientMachineDescription": "The name or IP address of the Orchestrator server that will handle GCP jobs. Example: orchestrator-server.example.com or 192.168.1.100.",
+                    "StorePathDescription": "The Google Cloud project ID, optionally appended with the region code if targeting a specific region. Example: my-project-id or my-project-id/us-central1."
                 }
             ]
         }