GITBOOK-328: change request with no subject merged in GitBook

cheqd · Oct 16, 2024 · 131cef2 · 131cef2
1 parent 2444bca
commit 131cef2
Show file tree

Hide file tree

Showing 3 changed files with 10 additions and 10 deletions.
diff --git a/studio/credentials/issue-credential.md b/studio/credentials/issue-credential.md
@@ -34,14 +34,14 @@ Within the JSON object of the API request, you will need to input the `issuer` a
 
 Users have two options for compiling the Credential bodies and issuing Verifiable Credentials:
 
-1. **Filling out a simple form** using the `application/x-www-url-form-encoded` option on the Swagger UI.
-2. **Compiling a Credential body yourself** using the `application/json` option on the Swagger UI.
+1. **Filling out a simple form** using the `application/x-www-url-form-encoded` option within an API client of your choice.
+2. **Compiling a Credential body yourself** using the `application/json` option within an API client of your choice.
 
 ### Option 1. Choose from a few variables and we will compile the Credential body for you
 
 This is the easiest way to issue Credentials and is recommended for users who are not overly familiar with compiling JSON objects.&#x20;
 
-Using the `application/x-www-url-form-encoded` option on the Swagger UI, users are able to choose between the following variables and options to issue Verifiable Credentials:
+Using the `application/x-www-url-form-encoded` option, users are able to choose between the following variables and options to issue Verifiable Credentials:
 
 <details>
 
@@ -229,7 +229,7 @@ Ensure that the `"statusPurpose"` and `"statusListName"` is the same as the exis
 
 ### Option 2. Publish a JSON payload yourself
 
-Instead of using simple form variables, you can issue a Verifiable Credential using a JSON payload with the `application/json` option on the Swagger UI.&#x20;
+Instead of using simple form variables, you can issue a Verifiable Credential using a JSON payload with the `application/json` option.&#x20;
 
 #### Request format
 

diff --git a/studio/dids/create-did.md b/studio/dids/create-did.md
@@ -16,8 +16,8 @@ Make sure you have set up your account with **cheqd Studio** and are logged in,
 
 Using the `/did/create` API, users have two options for creating a `did:cheqd` DID and associated DID Document on-ledger:
 
-1. **Filling out a simple form** using the `application/x-www-url-form-encoded` option on the Swagger UI
-2. **Compiling a DID Document body yourself** using the `application/json` option on the Swagger UI
+1. **Filling out a simple form** using the `application/x-www-url-form-encoded` option within an API client of your choice.
+2. **Compiling a DID Document body yourself** using the `application/json` option within an API client of your choice.
 
 {% swagger src="https://raw.githubusercontent.com/cheqd/credential-service/main/src/static/swagger-api.json" path="/did/create" method="post" expanded="true" %}
 [https://raw.githubusercontent.com/cheqd/credential-service/main/src/static/swagger-api.json](https://raw.githubusercontent.com/cheqd/credential-service/main/src/static/swagger-api.json)
@@ -27,7 +27,7 @@ Using the `/did/create` API, users have two options for creating a `did:cheqd` D
 
 This is the easiest way to create DIDs on cheqd and is recommended for users who are not overly familiar with compiling DID Documents.&#x20;
 
-Using the `application/x-www-url-form-encoded` option on the Swagger UI, users are able to choose between the following variables to compile your DID:
+Using the `application/x-www-url-form-encoded` option, users are able to choose between the following variables to compile your DID:
 
 <details>
 

diff --git a/studio/status-lists/status-list-v2021/create-status-list.md b/studio/status-lists/status-list-v2021/create-status-list.md
@@ -44,8 +44,8 @@ For the purpose of this tutorial, we will assume the user is creating an unencry
 
 Using the `/credential-status/create/unencrypted` API, users have two options for creating an encrypted Status List on-ledger:
 
-1. **Filling out a simple form** using the `application/x-www-url-form-encoded` option on the Swagger UI.
-2. **Compiling a Status List payload yourself** using the `application/json` option on the Swagger UI.
+1. **Filling out a simple form** using the `application/x-www-url-form-encoded` option within an API client of your choice.
+2. **Compiling a Status List payload yourself** using the `application/json` option within an API client of your choice.
 
 {% swagger src="https://raw.githubusercontent.com/cheqd/credential-service/main/src/static/swagger-api.json" path="/credential-status/create/unencrypted" method="post" expanded="true" %}
 [https://raw.githubusercontent.com/cheqd/credential-service/main/src/static/swagger-api.json](https://raw.githubusercontent.com/cheqd/credential-service/main/src/static/swagger-api.json)
@@ -55,7 +55,7 @@ Using the `/credential-status/create/unencrypted` API, users have two options fo
 
 This is the easiest way to create unencrypted Status Lists on cheqd and is recommended for users who are not overly familiar with compiling JSON objects.&#x20;
 
-Using the `application/x-www-url-form-encoded` option on the Swagger UI, users are able to choose between the following variables and options to create an unencrypted Status List on-ledger:
+Using the `application/x-www-url-form-encoded` option, users are able to choose between the following variables and options to create an unencrypted Status List on-ledger:
 
 <details>