[ZEPPELIN-6439] Fix typos and non-ASCII lookalike characters in interpreter documentation - #5506
Merged
Merged
Conversation
…preter documentation
Member
|
Merged into master (a424174). |
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
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 is this PR for?
Interpreter settings and documentation are shown directly to users in Zeppelin's UI and docs, but some of this text contains typos and non-ASCII lookalike characters.
The most notable case is the JDBC
default.completer.schemaFiltersdescription, which starts withСommausing a CyrillicС(U+0421) instead of the LatinC. It looks identical on screen, but it can break text search, copy-paste, and encoding-sensitive tooling. This PR replaces it with the LatinCin both the interpreter setting (interpreter-setting.json) and the corresponding docs (jdbc.md), so the two stay consistent.This PR also fixes the following typos:
seperated→separatedin the notebook authorization docsinteprreters→interpretersin thezeppelin.interpreter.include/zeppelin.interpreter.excludedescriptions ofconf/zeppelin-site.xml.templatephatomJs→PhantomJSin the Vagrant dev environment Ansible taskWording changes are kept minimal. Only description text is changed; no property keys, default values, or runtime behavior are affected. Following the issue guidance, generated files (e.g.
zeppelin-server/src/main/resources/zeppelin-site.xml) and vendored/minified assets are not modified.What type of PR is it?
Documentation
Todos
С(U+0421) inСomma separatedwith the LatinCin the JDBC interpreter setting and docsseperated→separatedin the notebook authorization docsinteprreters→interpreters(2 occurrences) inconf/zeppelin-site.xml.templatephatomJs→PhantomJSin the Vagrant dev environment Ansible taskWhat is the Jira issue?
ZEPPELIN-6439
How should this be tested?
Search the whole repository and confirm there are no matches:
Questions: