Flavio/refactor docs and tutorial

[faberga]

Proposed changes

Documentation and Tutorials update to match changes in PR (#64).

Types of changes

What types of changes does your code introduce to the HE Toolkit project?
Put an x in the boxes that apply

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update (if none of the other choices apply)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating
the PR. If you are unsure about any of them, do not hesitate to ask. We are
here to help! This is simply a reminder of what we are going to look for before
merging your code.

• I have read the CONTRIBUTING agreement
• Current formatting and unit tests / base functionality passes locally with my changes
• I have added tests that prove my fix is effective or that my feature works (if appropriate)
• I have added necessary documentation (if appropriate)
• Any dependent changes have been merged and published in downstream modules

[joserochh]

Why many of the .ker files are still there empty?

[kylanerace]

Why many of the .ker files are still there empty?

Are they empty? I mainly see the ones that were deleted

[kylanerace]

LGTM after correcting the file permission. I'm not seeing the blank .ker files @joserochh mentioned, but I may be overlooking them

[joserochh]

Why many of the .ker files are still there empty?

Are they empty? I mainly see the ones that were deleted

Oh that's right, my bad.

[kylanerace]

Typos fixed and otherwise. LGTM