Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Alphabetize glossary entries #16810

Merged
merged 1 commit into from
Mar 31, 2023
Merged

Conversation

michaeleby1
Copy link
Contributor

Description

Some of the Trino glossary entries were not in alphabetical order.
I moved them so that they are alphabetized correctly.

Additional context and related issues

Release notes

(x) This is not user-visible or docs only and no release notes are required.
( ) Release notes are required, please propose a release note for me.
( ) Release notes are required, with the following suggested text:

# Section
* Fix some things. ({issue}`issuenumber`)

@cla-bot cla-bot bot added the cla-signed label Mar 30, 2023
@michaeleby1 michaeleby1 requested review from mosabua and colebow March 30, 2023 18:04
Copy link
Member

@mosabua mosabua left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Simple move of content. No changes otherwise. Good to go. Thanks @michaeleby1

@mosabua mosabua requested a review from electrum March 30, 2023 19:33
@github-actions github-actions bot added the docs label Mar 30, 2023
:doc:`access control implementations </develop/system-access-control>`, and
other features of Trino.


Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: Remove a redundant empty line.

@ebyhr ebyhr force-pushed the me/alphabetize-glossary branch from 99da2c2 to f2b0891 Compare March 30, 2023 23:03
@ebyhr ebyhr merged commit 21a7a2c into trinodb:master Mar 31, 2023
@github-actions github-actions bot added this to the 412 milestone Mar 31, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

3 participants