github · gjtorikian · Mar 9, 2015 · Mar 9, 2015 · Mar 9, 2015 · Mar 9, 2015
diff --git a/enterprise/2.1/css/documentation.css b/enterprise/2.1/css/documentation.css
@@ -21,6 +21,10 @@ h1 {
   font-weight: normal;
 }
 
+body:not(.enterprise) .enterprise-only {
+  display: none;
+}
+
 .content h1 {
   font-weight: 300;
   -webkit-backface-visibility: hidden;

diff --git a/enterprise/2.1/guides/building-a-ci-server/index.html b/enterprise/2.1/guides/building-a-ci-server/index.html
@@ -143,7 +143,7 @@ <h2 id="writing-your-server">Writing your server</h2>
 HTTP header. We’ll only care about the PR events for now. From there, we’ll
 take the payload of information, and return the title field. In an ideal scenario,
 our server would be concerned with every time a pull request is updated, not just
-when it’s updated. That would make sure that every new push passes the CI tests.
+when it’s opened. That would make sure that every new push passes the CI tests.
 But for this demo, we’ll just worry about when it’s opened.</p>
 
 <p>To test out this proof-of-concept, make some changes in a branch in your test

diff --git a/enterprise/2.1/guides/getting-started/index.html b/enterprise/2.1/guides/getting-started/index.html
@@ -259,7 +259,7 @@ <h3 id="oauth">OAuth</h3>
 to create an OAuth token. Try pasting and running the following command:</p>
 
 <pre class="terminal">
-$ curl -i -u &lt;your_username&gt; -d '{"scopes": ["repo"], "note": "getting-started"}' \
+$ curl -i -u &lt;your_username&gt; -d '{"scopes": ["repo", "user"], "note": "getting-started"}' \
     https://api.github.com/authorizations
 
 HTTP/1.1 201 Created
@@ -268,7 +268,8 @@ <h3 id="oauth">OAuth</h3>
 
 {
   "scopes": [
-    "repo"
+    "repo",
+    "user"
   ],
   "token": "5199831f4dd3b79e7c5b7e0ebe75d67aa66e79d4",
   "updated_at": "2012-11-14T14:04:24Z",
@@ -293,7 +294,9 @@ <h3 id="oauth">OAuth</h3>
 a new token, we include an optional array of <a href="/enterprise/2.1/v3/oauth/#scopes"><em>scopes</em></a>, or access
 levels, that indicate what information this token can access. In this case,
 we’re setting up the token with <em>repo</em> access, which grants access to read and
-write to private repositories. See <a href="/enterprise/2.1/v3/oauth/#scopes">the scopes docs</a> for a full list of
+write to public and private repositories, and <em>user</em> scope, which grants read
+and write access to public and private user profile data. See
+<a href="/enterprise/2.1/v3/oauth/#scopes">the scopes docs</a> for a full list of
 scopes. You should <strong>only</strong> request scopes that your application actually needs,
 in order to not frighten users with potentially invasive actions. The <code>201</code>
 status code tells us that the call was successful, and the JSON returned
@@ -306,7 +309,7 @@ <h3 id="oauth">OAuth</h3>
 
 <pre class="terminal">
 $ curl -i -u &lt;your_username&gt; -H "X-GitHub-OTP: &lt;your_2fa_OTP_code&gt;" \
-    -d '{"scopes": ["repo"], "note": "getting-started"}' \
+    -d '{"scopes": ["repo", "user"], "note": "getting-started"}' \
     https://api.github.com/authorizations
 </pre>
 

diff --git a/enterprise/2.1/output/CNAME b/enterprise/2.1/output/CNAME
diff --git a/enterprise/2.1/output/changes.atom b/enterprise/2.1/output/changes.atom
diff --git a/enterprise/2.1/output/changes/2012-10-14-rate-limit-changes/index.html b/enterprise/2.1/output/changes/2012-10-14-rate-limit-changes/index.html
diff --git a/enterprise/2.1/output/changes/2012-10-17-org-members-redirection/index.html b/enterprise/2.1/output/changes/2012-10-17-org-members-redirection/index.html