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

Documentation Update #17

Closed
wants to merge 22 commits into from

Conversation

matthewspear
Copy link
Collaborator

I've done a quick tidy up of the README.md:

  • Caught a couple of typos
  • Corrected some commands
  • Added a clickable contents section
  • Added syntax highlighting

I have slightly changed the hierarchy, so let me know what you think!

Bruno Bodin and others added 21 commits August 31, 2018 08:47
Change `optionnal` to `optional`
Change `Les` to `Let`
Documentation mentions `make benchmark` which should be `make slambench`.
Sightly adjusted the hierarchy to provide quicker access to sections of the documentation via header links.

Moved FAQs down hierachy to more clearly explain what SLAMBench is at the beginning of the docuement and specific details further down.

Removed TODO List – this is better suited to either a GitHub issue or project board.

Few typos fixed: downdload, usescases and repart.
`?` were causing problems in the links.
Updated headers to single sided hashes, fixing issue with visible hashes.

Converted inline code references to single backticks instead of multiple.

Added syntax highlighting for code blocks by listing keyword type after opening backticks.
Changed if checking from -f to -d since it is checking directories and not files and was previously showing not found for any of the usecases regardless of their actual status.

Removed some surplus -e parameters that were being displayed as text.
@mihaibujanca
Copy link
Owner

For this PR I feel like it's probably better if we make a PR straight to the main pamela repository. It's likely that it will take some time before we integrate everything that's being pushed to master on this repository, and these changes will be useful for anyone using the framework before we get to push the new stuff.

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

Successfully merging this pull request may close these issues.

3 participants