fix(ui): Fix typo in Laravel onboarding text #103896
Merged
Conversation
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
github-actions
bot
added
the
Scope: Frontend
shellmayr
approved these changes
Nov 26, 2025
Member
shellmayr
left a comment
shellmayr
left a comment
There was a problem hiding this comment.
Thanks for fixing - as it's mentioned in the PR description, the tct() function handles translation automatically, so there's no need to update anything else.
shellmayr
added
the
Trigger: getsentry tests
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Description
This PR fixes a typo in the Laravel SDK onboarding ("11.0 an up" -> "11.0 and up").
The fix was applied to:
static/app/gettingStartedDocs/php-laravel/onboarding.tsxstatic/app/gettingStartedDocs/php-laravel/profiling.tsxNote: I updated the source
.tsxfiles but did not manually update thedjango.potranslation files, assuming the build system will handle the synchronization.Legal Boilerplate
Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.