Fix incorrect expression for Zone Lockdown example #19452
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
Contributor
|
Thank you for the fix, @connorgurney-personal! |
pedrosousa
approved these changes
Jan 27, 2025
workers-devprod
added
the
contribution
|
Congratulations @connorgurney-personal, the maintainer of this repository has issued you a holobyte! Here it is: https://holopin.io/holobyte/cm6fadp93179350clbuxj6wdtq This badge can only be claimed by you, so make sure that your GitHub account is linked to your Holopin account. You can manage those preferences here: https://holopin.io/account. |
deadlypants1973
pushed a commit
that referenced
this pull request
Jan 29, 2025
kodster28
pushed a commit
that referenced
this pull request
Jan 30, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
This is a minor change that ensures that the expression matches the example on the page. Given how little I’ve changed, it naturally adheres to the documentation style guide.