style: standardize on "service" for Beamable product capabilities (v5.0)#61
Open
allister-beamable wants to merge 1 commit intounity/v5.0from
Open
style: standardize on "service" for Beamable product capabilities (v5.0)#61allister-beamable wants to merge 1 commit intounity/v5.0from
allister-beamable wants to merge 1 commit intounity/v5.0from
Conversation
Replace "feature" with "service" as the noun for Beamable product capabilities across all beamable-services/ pages. Rationale: the nav section is already "Beamable Services"; "service" aligns with the engineering-oriented audience and the existing structural vocabulary. Preserved: "Feature Support" table headers, "feature prefab/Prefab" (Unity asset references), occurrences in code blocks, and any use of "feature" referring to non-Beamable concepts. Scope: docs/unity/user-reference/beamable-services/ only. Whatsnew/, portal/, and CLI guide pages are intentionally excluded. 71 substitutions across 29 files. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
allister-beamable
force-pushed
the
style/feature-to-service-v5.0
branch
from
d2ecef4 to
9c693f7
Compare
| ## A/B Testing API | ||
|
|
||
| Unlike many Beamable Features, A/B Testing does not require a specific Beamable Feature Prefab to be used. The main entry point to this feature is C# programming. | ||
| Unlike many Beamable services, A/B Testing does not require a specific Beamable Feature Prefab to be used. The main entry point to this service is C# programming. |
Contributor
Author
There was a problem hiding this comment.
Suggested change
| Unlike many Beamable services, A/B Testing does not require a specific Beamable Feature Prefab to be used. The main entry point to this service is C# programming. | |
| Unlike many Beamable services, A/B Testing does not require a specific Beamable Feature Prefab to be used. The main entry point to A/B testing is C# programming. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
docs/unity/user-reference/beamable-services/pagesScope and exclusions
Changed:
docs/unity/user-reference/beamable-services/onlyIntentionally excluded:
whatsnew/— "new feature" is universal product/changelog vocabulary, leave itportal/— operator audience, less technical, leave itPreserved within scope:
Review notes
Please flag any substitution that reads awkwardly or that you feel should remain "feature" — this is a style policy discussion as much as an edit, and Eva/Chris/Balbio's input on the policy is the point of this PR.
The v5.1 counterpart is beamable/docs#— (see style/feature-to-service-v5.1).
🤖 Generated with Claude Code