fix: typo

HYCHAIN · Oct 10, 2024 · a79b996 · a79b996
1 parent 36c4730
commit a79b996
Show file tree

Hide file tree

Showing 2 changed files with 2 additions and 2 deletions.
diff --git a/private-spec.json b/private-spec.json
@@ -1928,7 +1928,7 @@
       "post": {
         "operationId": "createLeaderboardScore",
         "summary": "Create leaderboard score",
-        "description": "Create a score for the provided leaderboardId. Leaderboard scores can be provided for any user id when the app secret key authorization is provided. Alternatively, a user may submit their own scores by provided their session authorization, with a request body containing `score` and `hash`. A valid `hash` is intended to be generated for each score within the game client as sha256(leaderboardKey:userId:score:scoreType). If scoreType is ommitted, the hash should be generated as sha256(leaderboardKey:userId:score).",
+        "description": "Create a score for the provided leaderboardId. Leaderboard scores can be provided for any user id when the app secret key authorization is provided. Alternatively, a user may submit their own scores by provided their session authorization, with a request body containing `score` and `hash`. A valid `hash` is intended to be generated for each score within the game client as sha256(leaderboardKey:userId:score:scoreType). If scoreType is omitted, the hash should be generated as sha256(leaderboardKey:userId:score).",
         "tags": [
           "Leaderboards"
         ],

diff --git a/spec.json b/spec.json
@@ -1928,7 +1928,7 @@
       "post": {
         "operationId": "createLeaderboardScore",
         "summary": "Create leaderboard score",
-        "description": "Create a score for the provided leaderboardId. Leaderboard scores can be provided for any user id when the app secret key authorization is provided. Alternatively, a user may submit their own scores by provided their session authorization, with a request body containing `score` and `hash`. A valid `hash` is intended to be generated for each score within the game client as sha256(leaderboardKey:userId:score:scoreType). If scoreType is ommitted, the hash should be generated as sha256(leaderboardKey:userId:score).",
+        "description": "Create a score for the provided leaderboardId. Leaderboard scores can be provided for any user id when the app secret key authorization is provided. Alternatively, a user may submit their own scores by provided their session authorization, with a request body containing `score` and `hash`. A valid `hash` is intended to be generated for each score within the game client as sha256(leaderboardKey:userId:score:scoreType). If scoreType is omitted, the hash should be generated as sha256(leaderboardKey:userId:score).",
         "tags": [
           "Leaderboards"
         ],