Skip to content

grammar fixes: there's -> there are #10

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.

Sign up for GitHub

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

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

grammar fixes: there's -> there are #10

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 5 additions & 5 deletions public/code.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -37,7 +37,7 @@
<h1>Writing LTI Stuff</h1>

<p>
This page goes over the basics of creating an app that leverages LTI. There's
This page goes over the basics of creating an app that leverages LTI. There are
a lot of great links at the bottom that may help out, but it's probably a good
idea to at least read the intro first to get a feel for what LTI does exactly.
</p>
Expand Down Expand Up @@ -120,17 +120,17 @@ <h2>Introduction</h2>
<a name="building"></a>
<h2>Building an LTI App</h2>
<p>If you want to build an LTI-compliant app or <span class='label label-info'>provider</span>
then there's really only a couple things you need to worry about: how users can
then there are really only a couple things you need to worry about: how users can
configure your app, how to accept a launch from a <span class='label label-warning'>consumer</span>,
and potentially handling some of the extra goodies LTI makes possible.</p>

<h3>App Configuration</h3>
<p>App configuration is <a href="/tutorials.html">different for every LMS</a> right
now, but we're working on that. The best way to provide a standard configuration
for your app is by providing a url that returns an xml configuration for your
app. There's a lot of
app. There are a lot of
<a href="https://canvas.instructure.com/doc/api/tools_xml.html">examples of app
configurations in the Canvas API documentation</a>. Remember, if there's custom
configurations in the Canvas API documentation</a>. Remember, if there are custom
values you want to make sure come across with every user, this is the place
to include them. The only really crucial piece to specify is the url endpoint that will
accept the POST requests, <code>blti:launch_url</code>.</p>
Expand Down Expand Up @@ -161,7 +161,7 @@ <h3>App Launch</h3>
some trouble if you can find a library to do the work for you.</p>

<h3>Extras</h3>
<p>This page has described the most basic type of LTI integration. There's a number of
<p>This page has described the most basic type of LTI integration. There are a number of
other things you can do on top of this, including passing scores from the
<span class='label label-info'>provider</span> back to the gradebook of the
</span class='label label-warning'>consumer</span>, or adding buttons to the
Expand Down