Skip to content

Commit

Permalink
Fix typos (#5)
Browse files Browse the repository at this point in the history
## Changes

Fixes typos within the cloud docs.

## Checks

By submitting your pull request for review, you agree to the following:

- [x] This contribution was created in whole or in part by me, and I
have the right to submit it under the terms of this repository's open
source licenses.
- [x] I understand and agree that this contribution and a record of it
are public, maintained indefinitely, and may be redistributed under the
terms of this repository's open source licenses.
- [x] To the best of my knowledge, all proposed changes are accurate.
  • Loading branch information
Sleitnick authored Aug 29, 2023
1 parent 7a13cad commit 4a8849f
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 4 deletions.
4 changes: 2 additions & 2 deletions content/en-us/cloud/open-cloud/data-store-api-handling.md
Original file line number Diff line number Diff line change
Expand Up @@ -206,7 +206,7 @@ Ordered Data Stores endpoints use [Perfect-Encoding](https://www.rfc-editor.org/

### Universe ID

The **Universe ID** is the unique identifier of the experience in which you want to access your data stores. The value of an experience's Universe ID is the value of its `Class.DataModel.GameId`, **not** the same as the **Startting Place ID**, which identifies the starting place of an experience rather than the entire experience.
The **Universe ID** is the unique identifier of the experience in which you want to access your data stores. The value of an experience's Universe ID is the value of its `Class.DataModel.GameId`, **not** the same as the **Starting Place ID**, which identifies the starting place of an experience rather than the entire experience.

You can obtain the **Universe ID** of an experience with the following steps:

Expand All @@ -220,7 +220,7 @@ You can obtain the **Universe ID** of an experience with the following steps:
You can organize your data stores by setting a unique string as a scope that specifies a subfolder for the entry. Once you set a scope, it automatically prepends to all keys in all operations done on the data store. Scopes are optional and by default as `global` for standard data stores but required for ordered data stores.

<Alert severity="warning">
It is **strongly recommended** to use `prefix` paramaters instead of `scope` for sorting and listing **standard** data stores.
It is **strongly recommended** to use the `prefix` parameter instead of `scope` for sorting and listing **standard** data stores.
</Alert>

The scope categorizes your data with a string and a separator with "/", such as:
Expand Down
4 changes: 2 additions & 2 deletions content/en-us/cloud/webhooks/automate-right-to-erasure.md
Original file line number Diff line number Diff line change
Expand Up @@ -136,7 +136,7 @@ After you finish setting up the webhook, bot, and API key for data stores, add t
DISCORD_BOT_TOKEN = ""
GUILDED_BOT_TOKEN = ""
OPEN_CLOUD_API_KEY = ""
ROBOLOX_WEBHOOK_SECRET = ""
ROBLOX_WEBHOOK_SECRET = ""
# Dictionary of the Start place ID to
# (universe ID, list of (data stores name, scope, and entry key)) for
Expand Down Expand Up @@ -281,7 +281,7 @@ After you finish setting up the webhook, bot, and API key for data stores, add t
# Validates signature
timestamp_message = "{}.{}".format(timestamp, message.embeds[0].description)
digest = hmac.new(
bot_config.ROBOLOX_WEBHOOK_SECRET.encode(),
bot_config.ROBLOX_WEBHOOK_SECRET.encode(),
msg=timestamp_message.encode(),
digestmod=hashlib.sha256
).digest()
Expand Down

0 comments on commit 4a8849f

Please sign in to comment.