This is an automated email from the ASF dual-hosted git repository.

jshao pushed a commit to branch branch-1.0
in repository https://gitbox.apache.org/repos/asf/gravitino.git


The following commit(s) were added to refs/heads/branch-1.0 by this push:
     new c3d4eb9cce [#8521] fix(doc): Fix the doc style issue (#8532)
c3d4eb9cce is described below

commit c3d4eb9ccef32bf36929f82318b782c90742ad66
Author: github-actions[bot] 
<41898282+github-actions[bot]@users.noreply.github.com>
AuthorDate: Thu Sep 11 19:25:52 2025 +0800

    [#8521] fix(doc): Fix the doc style issue (#8532)
    
    ### What changes were proposed in this pull request?
    
    Fix the doc style issue when building the dco.
    
    ### Why are the changes needed?
    
    Fix: #8521
    
    ### Does this PR introduce _any_ user-facing change?
    
    No.
    
    ### How was this patch tested?
    
    Existing CI.
    
    Co-authored-by: Jerry Shao <[email protected]>
---
 docs/manage-jobs-in-gravitino.md                     |  5 ++++-
 docs/open-api/jobs.yaml                              | 20 ++++++++++----------
 docs/security/how-to-authenticate.md                 |  4 ++--
 ...e-partitioning-distribution-sort-order-indexes.md | 13 ++-----------
 4 files changed, 18 insertions(+), 24 deletions(-)

diff --git a/docs/manage-jobs-in-gravitino.md b/docs/manage-jobs-in-gravitino.md
index 582d9a5cd2..6d1a52236f 100644
--- a/docs/manage-jobs-in-gravitino.md
+++ b/docs/manage-jobs-in-gravitino.md
@@ -2,7 +2,10 @@
 title: "Manage jobs in Gravitino"
 slug: /manage-jobs-in-gravitino
 date: 2025-08-13
-keywords: job, job template, gravitino
+keywords:
+  - job
+  - job template
+  - gravitino
 license: "This software is licensed under the Apache License version 2."
 ---
 
diff --git a/docs/open-api/jobs.yaml b/docs/open-api/jobs.yaml
index f6d1ec2db6..d5be5bc109 100644
--- a/docs/open-api/jobs.yaml
+++ b/docs/open-api/jobs.yaml
@@ -66,7 +66,7 @@ paths:
       description: Registers a job template in the specified metalake
       requestBody:
         content:
-          application/json:
+          application/vnd.gravitino.v1+json:
             schema:
               $ref: "#/components/requests/JobTemplateRegisterRequest"
             examples:
@@ -107,9 +107,9 @@ paths:
             application/vnd.gravitino.v1+json:
               schema:
                 $ref: "#/components/responses/JobTemplateResponse"
-                examples:
-                  JobTemplateResponse:
-                    $ref: "#/components/examples/JobTemplateResponse"
+              examples:
+                JobTemplateResponse:
+                  $ref: "#/components/examples/JobTemplateResponse"
         "404":
           description: Not Found - The specified job template does not exist 
in the specified metalake
           content:
@@ -224,9 +224,9 @@ paths:
             application/vnd.gravitino.v1+json:
               schema:
                 $ref: "#/components/responses/JobResponse"
-                examples:
-                  JobResponse:
-                    $ref: "#/components/examples/JobResponse"
+              examples:
+                JobResponse:
+                  $ref: "#/components/examples/JobResponse"
         "404":
           description: Not Found - The specified job does not exist in the 
specified metalake
           content:
@@ -254,9 +254,9 @@ paths:
             application/vnd.gravitino.v1+json:
               schema:
                 $ref: "#/components/responses/JobResponse"
-                examples:
-                  JobResponse:
-                    $ref: "#/components/examples/JobResponse"
+              examples:
+                JobResponse:
+                  $ref: "#/components/examples/JobResponse"
         "404":
           description: Not Found - The specified job does not exist in the 
specified metalake
           content:
diff --git a/docs/security/how-to-authenticate.md 
b/docs/security/how-to-authenticate.md
index 4fecf65d45..d6e92bde4e 100644
--- a/docs/security/how-to-authenticate.md
+++ b/docs/security/how-to-authenticate.md
@@ -283,7 +283,7 @@ docker run -dti -p 8080:8080 -e 
KC_BOOTSTRAP_ADMIN_USERNAME=admin -e KC_BOOTSTRA
 
     ![create-realm.png](../assets/security/create-realm.png)
 
-4. Get the `gravitinorealm` public key, which is the <the default signing key> 
in gravitino.conf
+4. Get the `gravitinorealm` public key, which is the `<the default signing 
key>` in gravitino.conf
    Access `http://localhost:8080/realms/gravitinorealm` in browser
 
    ![realm-public-key.png](../assets/security/realm-public-key.png)
@@ -364,4 +364,4 @@ Use the access token to make requests to the Gravitino 
server
 
 ```shell
 curl -v -X GET -H "Accept: application/vnd.gravitino.v1+json" -H 
"Content-Type: application/json" -H "Authorization: Bearer <access_token>" 
http://localhost:8090/api/version
-``` 
\ No newline at end of file
+```
diff --git a/docs/table-partitioning-distribution-sort-order-indexes.md 
b/docs/table-partitioning-distribution-sort-order-indexes.md
index 581d10fc3a..d27213ba18 100644
--- a/docs/table-partitioning-distribution-sort-order-indexes.md
+++ b/docs/table-partitioning-distribution-sort-order-indexes.md
@@ -81,14 +81,8 @@ To create a distribution(bucketed) table, you should use the 
following three com
 
 ```java
 Distributions.of(Strategy.HASH, 4, NamedReference.field("score"));
-```
-
-</TabItem>
-
-<TabItem value="java" label="Java">
-if you want to use auto distribution, you can use the following code, it will 
set the number is -1.
 
-```java
+// if you want to use auto distribution, you can use the following code, it 
will set the number is -1.
 // Auto distribution with strategy and fields
 Distributions.auto(Strategy.HASH, NamedReference.field("score"));
 ```
@@ -96,9 +90,6 @@ Distributions.auto(Strategy.HASH, 
NamedReference.field("score"));
 
 </Tabs>
 
-
-
-
 ## Sort ordering
 
 To define a sorted order table, you should use the following three components 
to construct a valid sorted order table.
@@ -359,4 +350,4 @@ tableCatalog.createTable(
 ```
 
 </TabItem>
-</Tabs>
\ No newline at end of file
+</Tabs>

Reply via email to