Skip to content

Commit 8fd50a8

Browse files
allister-beamableclaude
allister-beamable
and
claude
committed
Grammar pass: capitalize Portal as a proper noun.
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
1 parent 121f6f2 commit 8fd50a8

32 files changed

Lines changed: 52 additions & 52 deletions

‎docs/cli/guides/ms-logging.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -68,7 +68,7 @@ The `Log` type has methods for each type of log level.
6868

6969
In version 6.0+, you can override the log level per request based on the player calling your Microservice, or the path being invoked on the service. By default, the log level for the entire service is _Information_, but if there was an error-prone route, or a specific user was experiencing issues, you could set the log level to _Debug_ for that use case, without affecting the log level for anything else.
7070

71-
To set a dynamic log level, go to the Portal's microservice page, and create a new _Log Config Rule_. Once you create a rule, the Microservice will automatically update to emit logs at the new level. It may take a few seconds for the log level to change.
71+
To set a dynamic log level, go to Portal's microservice page, and create a new _Log Config Rule_. Once you create a rule, the Microservice will automatically update to emit logs at the new level. It may take a few seconds for the log level to change.
7272

7373
### Attributes
7474

‎docs/cli/guides/ms-routing.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -73,7 +73,7 @@ var scope = cid + '.' + pid;
7373
```
7474
#### Authorization
7575

76-
Finally, while not required, it is important to send an HTTP authorization header in the form of a Bearer token. The bearer token should be a valid access token for a Beamable Player. These tokens can be fetched from the Portal, or you can use the following command to view the token information from a local beamable CLI project.
76+
Finally, while not required, it is important to send an HTTP authorization header in the form of a Bearer token. The bearer token should be a valid access token for a Beamable Player. These tokens can be fetched from Portal, or you can use the following command to view the token information from a local beamable CLI project.
7777

7878
```sh
7979
cat .beamable/temp/auth.beam.json

‎docs/cli/guides/upgrading.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -40,7 +40,7 @@ There are no compile time breaking changes between 5.x and 6.0. However, there a
4040
#### Microservice Logging Changes
4141
The 6.0 release completely changes the way that Microservices send and store log information. Previously, Microservices sent logs in a proprietary format to Amazon Cloud Watch. In the new release, logs are formatted as standard [open telemetry](https://opentelemetry.io/docs/specs/otel/logs/) data, and sent to a log warehouse via an [otel collector](https://opentelemetry.io/docs/collector/). The change is transparent to the Microservice layer, and you do not need to make any changes to enable the new logs.
4242

43-
When you upgrade your service to 6.0, you will begin to see a new log workflow in the Portal. **Your old logs will not be available**. Only the new logs are available. Beamable only retains log data for 2 weeks anyway, but if you _must_ have access to your existing 2 weeks of log information, you will need Pro Support, and you must reach out directly to Beamable Support.
43+
When you upgrade your service to 6.0, you will begin to see a new log workflow in Portal. **Your old logs will not be available**. Only the new logs are available. Beamable only retains log data for 2 weeks anyway, but if you _must_ have access to your existing 2 weeks of log information, you will need Pro Support, and you must reach out directly to Beamable Support.
4444

4545
#### Telemetry Warning
4646
The 6.0 CLI will collect usage data and send it back to Beamable. By default, the CLI will ask you to opt into sending the usage information. The result of your selection is stored in the `.beamable/otel-config.json` file. You can change the `BeamCliAllowTelemetry` property to opt in or out of the usage collection.

‎docs/portal/portal-announcements.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -8,7 +8,7 @@ Follow these steps to access and configure Announcements:
88

99
| Step | Detail |
1010
| :------------------------ | :--------------------------------------- |
11-
| 1. Open the Portal | • See Portal documentation for more info |
11+
| 1. Open Portal | • See Portal documentation for more info |
1212
| 2. Navigate via sidebar | • Click "Announcements" |
1313
| 3. Configure the settings | • Enjoy! |
1414

‎docs/portal/portal-cloud-data.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,15 +1,15 @@
11
# Cloud Data
22

33

4-
The Cloud Save feature allows you to manage and configure cloud data storage for your game through the Portal.
4+
The Cloud Save feature allows you to manage and configure cloud data storage for your game through Portal.
55

66
## Getting Started
77

88
Follow these steps to configure cloud data settings:
99

1010
| Step | Detail |
1111
| :----------------------------------------- | :--------------------------------------- |
12-
| 1. Open the Portal | • See Portal documentation for more info |
12+
| 1. Open Portal | • See Portal documentation for more info |
1313
| 2. Expand "Operate" section on the sidebar | • Click "Game Base Cloud Data" |
1414
| 3. Configure the settings | • Enjoy! |
1515

‎docs/portal/portal-groups.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,14 @@
11
# Groups
22

3-
The Groups feature allows you to organize and manage player groups through the Portal.
3+
The Groups feature allows you to organize and manage player groups through Portal.
44

55
## Getting Started
66

77
Follow these steps to configure Groups settings:
88

99
| Step | Detail |
1010
| :---------------------------------------- | :--------------------------------------- |
11-
| 1. Open the Portal | • See Portal documentation for more info |
11+
| 1. Open Portal | • See Portal documentation for more info |
1212
| 2. Expand "Engage" section on the sidebar | • Click "Groups" |
1313
| 3. Configure the settings | • Enjoy! |
1414

‎docs/portal/portal-in-app-purchases.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,14 @@
11
# In-App Purchases
22

3-
The Store feature's In-App Purchases can be managed and configured through the Portal.
3+
The Store feature's In-App Purchases can be managed and configured through Portal.
44

55
## Getting Started
66

77
Follow these steps to configure In-App Purchases settings:
88

99
| Step | Detail |
1010
| :------------------------------------------ | :--------------------------------------- |
11-
| 1. Open the Portal | • See Portal documentation for more info |
11+
| 1. Open Portal | • See Portal documentation for more info |
1212
| 2. Expand "Monetize" section on the sidebar | • Click "Real-Money Transactions" |
1313
| 3. Configure the settings | • Enjoy! |
1414

‎docs/portal/portal-inventory.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,14 @@
11
# Inventory
22

3-
The Inventory feature can be managed from the Portal.
3+
The Inventory feature can be managed from Portal.
44

55
## Getting Started
66

77
Follow these steps to manage player inventory:
88

99
| Step | Detail |
1010
| :---------------------------------------- | :---------------------------------------------------- |
11-
| 1. Open the Portal | • See [Portal](doc:portal) for more info |
11+
| 1. Open Portal | • See [Portal](doc:portal) for more info |
1212
| 2. Expand "Engage" section on the sidebar | • Click "Players" |
1313
| 3. Navigate to a player's profile page | • Scroll the list or search by playerId, device, etc. |
1414
| 4. Open the player's Inventory page | • Click "Inventory" on the navigation panel |

‎docs/portal/portal-leaderboards.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,14 @@
11
# Leaderboards
22

3-
The Leaderboards feature can be managed from the Portal.
3+
The Leaderboards feature can be managed from Portal.
44

55
## Getting Started
66

77
Follow these steps to manage leaderboards:
88

99
| Step | Detail |
1010
| :---------------------------------------- | :--------------------------------------- |
11-
| 1. Open the Portal | • See [Portal](doc:portal) for more info |
11+
| 1. Open Portal | • See [Portal](doc:portal) for more info |
1212
| 2. Expand "Engage" section on the sidebar | • Click "Leaderboards" |
1313
| 3. Configure the settings | • Enjoy! |
1414

‎docs/portal/portal-players.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,14 +1,14 @@
11
# Players
22

3-
The Admin feature's **Players** section can be managed from the Portal.
3+
The Admin feature's **Players** section can be managed from Portal.
44

55
## Getting Started
66

77
Follow these steps to manage players:
88

99
| Step | Detail |
1010
| :-------------------------------------------- | :--------------------------------------- |
11-
| 1. Open the Portal | • See [Portal](doc:portal) for more info |
11+
| 1. Open Portal | • See [Portal](doc:portal) for more info |
1212
| 2. Expand the "Engage" section on the sidebar | • Click "Players" |
1313
| 3. Configure the settings | • Enjoy! |
1414

0 commit comments

Comments
 (0)