Fix segment enabled json examples

JSON requires lowercase booleans.

Change-Id: If0a14f4943a4c9107ddb4de4655315e393b8edce

api-ref/source/failover-segments.inc

@@ -100,7 +100,7 @@ recovery_method. For `service_type` user can mention the name of service for
 which this segment is created. As of now user can mention `COMPUTE` as
 `service_type`. For `recovery_method` user can mention either `auto`,
 `reserved_host`, `auto_priority` or `rh_priority`. Segment name should be
-unique. For `enabled` user can mention `True` or `False` to enable/disable
+unique. For `enabled` user can mention `true` or `false` to enable/disable
 this segment.
 
 Response Codes

doc/api_samples/segments/segment-create-req.json

@@ -3,6 +3,6 @@
         "service_type": "COMPUTE",
         "recovery_method": "auto",
         "name": "new_segment",
-        "enabled": True
+        "enabled": true
     }
 }

doc/api_samples/segments/segment-create-resp.json

@@ -10,6 +10,6 @@
         "deleted_at": null,
         "id": 4,
         "name": "new_segment",
-        "enabled": True
+        "enabled": true
     }
 }

doc/api_samples/segments/segment-get-resp.json

@@ -10,6 +10,6 @@
         "deleted_at": null,
         "id": 4,
         "name": "new_segment",
-        "enabled": True
+        "enabled": true
     }
 }

doc/api_samples/segments/segment-update-req.json

@@ -1,6 +1,6 @@
 {
     "segment": {
         "name": "new_segment",
-        "enabled": False
+        "enabled": false
     }
 }

doc/api_samples/segments/segment-update-resp.json

@@ -10,6 +10,6 @@
         "deleted_at": null,
         "id": 4,
         "name": "new_segment",
-        "enabled": False
+        "enabled": false
     }
 }

doc/api_samples/segments/segments-list-resp.json

@@ -11,7 +11,7 @@
             "deleted_at": null,
             "id": 1,
             "name": "segment2",
-            "enabled": True
+            "enabled": true
         }
     ]
 }