bbrcknl

@lsf37 @Indanz Just to be clear, should the `name` and `manual_name` be the same, and in camelCase, e.g. ```` ````

@Indanz @lsf37 > | Error Code | Possible Cause | > | :- | :- | > | seL4_IllegalOperation | The _service is a CPtr to a capability of the...

@Indanz I've attempted a fix, pls see https://github.com/seL4/seL4/pull/1151 But it's made the error codes long and clunky. Any hints/suggestions would be helpful.

@Indan Zupancic Thanks for the xinclude code I've tried to use it to include a test fail, but have unfortunately failed. Can you please take a look at the files...

@Indanz Can you pls check over the first draft of the glossary for the seL4 manual?

> I assume the glossary us based off the one we have in the [abstract spec](https://github.com/seL4/l4v/blob/master/spec/abstract/Glossary_Doc.thy)? > > I haven't looked through everything yet, but I'd like to before we...

@Indanz > In the preview you gave it looked great, good work! Thanks! > > To-dos: > > ``` > > * The new tutorial md files _are not_ those...

The tutorials have now been updated to fit into the new tutorial structure as per this PR (#231). The new tutorials: https://github.com/seL4/sel4-tutorials/pull/106 A note on using the rewritten docsite (#231):...

> * The new inline solutions and the resulting how-to guide are really cool! Thanks! > * I still need to go through all the parts, but I also like...

Renaming the GettingStarted directory to Resources will break a number of links pointing to the docsite. Repos that will need updating: - sel4/camkes-vm-examples-manifest - sel4/seL4 - sel4/seL4_tools - sel4/sel4bench-manifest -...