Update one-time-password-sms.yaml following Tanja review

Removed termsOfService and contact fields 
Fixed servers

code/API_definitions/one-time-password-sms.yaml

@@ -22,23 +22,15 @@ info:
     It is important to remark that in cases where personal user data is processed by the API, and users can exercise their rights through mechanisms such as opt-in and/or opt-out, the use of 3-legged access tokens becomes mandatory. This measure ensures that the API remains in strict compliance with user privacy preferences and regulatory obligations, upholding the principles of transparency and user-centric data control.
 
   version: 1.0.0-rc.1
-  termsOfService: http://example.com/terms/
-  contact:
-    name: API Support
-    url: http://www.example.com/support
-    email: support@example.com
   license:
     name: Apache 2.0
     url: https://www.apache.org/licenses/LICENSE-2.0.html
 servers:
-  - url: https://{host}{basePath}
+  - url: {apiRoot}/one-time-password-sms/v1rc1
     variables:
-      host:
-        default: api.example.com
-        description: Host that serves the API
-      basePath:
-        default: /one-time-password-sms/v0
-        description: Base path for the one time password sms API
+      apiRoot:
+        default: http://localhost:9091
+        description: API root, defined by the service provider, e.g. `api.example.com` or `api.example.com/somepath`
 tags:
   - name: OTP Management
     description: API operations to manage OTP codes
@@ -240,7 +232,7 @@ components:
       content:
         application/json:
           schema:
-            $ref: '#/components/schemas/ErrorInfo'
+            $ref: '#/components/schemas/Error'
           example:
             status: 400
             code: INVALID_ARGUMENT