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

Should we add a Glossary to the book? #6

Open
kbeyls opened this issue Sep 16, 2021 · 1 comment
Open

Should we add a Glossary to the book? #6

kbeyls opened this issue Sep 16, 2021 · 1 comment
Labels
content New content for the book

Comments

@kbeyls
Copy link
Member

kbeyls commented Sep 16, 2021

No description provided.

@kbeyls kbeyls added the content New content for the book label Sep 16, 2021
@sam-ellis
Copy link
Collaborator

I think it depends on how many terms exist that need explaining and whether these are used throughout the book that warrants a glossary definition or whether they are localized such that a local definition will suffice. Thus far I think we have the term "side-channel" that would benefit from a glossary definition. Perhaps if we can reach (say) 5 such terms, then a glossary is beneficial.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content New content for the book
Projects
None yet
Development

No branches or pull requests

2 participants