Merge pull request #7 from adlnet/master

update garemoko master to adlnet
Added headings for required additional endpoints
Revert "Added headings for required additional endpoints"

This reverts commit 40d6aa4718253c5a31c3110523da49c5b4de570f.
Merge pull request #8 from adlnet/master

grabbing typo fix
Add 'progress' to 'result'

I have a use case on a real live project to report both 
page progress and score for a SCORM-style course. I imagine 
this is a common use case. I'm surprised this hasn't come up 
before actually. 

I think the solution proposed is quite neat and simple. I don't
think an extension would be appropriate for something so common.
changed language of score and progress; reordered result properties

I did consider having just one score object property and changing its use based on verb, but since we have separate completion and success properties, I thought separate progress and score properties made sense too. 
full stops
Added 'units' property to 'score' object

also fixed a mis-written </tr> and inconsistent capitalisation. 
removed progress and units
Changed activity to experience. Toned down reference to extension.
removed last TCAPI reference and replaced with xAPI
Merge pull request #50 from nhruska/master

removed last TCAPI reference in examples and replaced with xAPI
Merge pull request #49 from paul-esch/master

Chapter 3: Definitions
Merge pull request #40 from garemoko/pageViewTracking

Page view tracking
restructured section 4.1.10 Voided

As in my previous merges, I restructured the section for added clarity.
Please check for completeness and correctness. Note that I changed
'should' into 'must' in the original sentence that read: 'should mark
the target statement as voided using the "voided" field.' (line 1226)

I.m.h.o a core functionality as this is not optional. By all means,
change back to SHOULD if MUST is too stringent; I did not follow all
discussion around this.