Clarify LPM CLI branding#390
Merged
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
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.
What changed
Clarifies user-facing wording so it consistently identifies LPM CLI, LPM Firewall, and the LPM.dev Registry where that distinction helps users.
Why
The previous copy used the broad “LPM” label in prompts, warnings, and diagnostic guidance, which could be ambiguous alongside related LPM services.
Impact
No behavior changes. This updates CLI-facing text and its focused copy assertion only.
Validation
cargo test -p lpm-cli --locked firewall_wizard_copy_uses_npm_package_language