CORE-1715 Change development site texts and main page - cloud video to video streaming

Author: bkarolyi

Overview.md

@@ -1,12 +1,12 @@
 # Overview
-IBM Cloud Video allows third-party clients to access IBM Cloud Video users' resources (data) via a HTTP-based (RESTful) API. It also provides a Broadcaster Library that is capable of broadcasting to a user's channel. Both the REST API and the Broadcaster Library uses the OAuth 2.0 protocol for authentication and authorization.
+IBM Video Streaming allows third-party clients to access IBM Video Streaming users' resources (data) via a HTTP-based (RESTful) API. It also provides a Broadcaster Library that is capable of broadcasting to a user's channel. Both the REST API and the Broadcaster Library uses the OAuth 2.0 protocol for authentication and authorization.
 
 ## Basic workflow
 The basic workflow of a third-party Client is the following:
 
 1. **Authorize the user:** Obtain and validate the user's credentials (username and password). The client must never store these credentials, only pass it to the server for authorization.
-2. **Obtain an access token:** If the user's credentials were entered correctly, the third-party client can obtain an access token. Once this token is received, it can be used to access the user's resources until the token expires or the user revokes it on the IBM Cloud Video website.
-3. **Access the user's resources:** The client can use Ustream's REST API or the IBM Cloud Video Broadcasting Library to access the user's resources (data) or to broadcast to the user's channel. The client authorizes itself using the access token, with methods described by the OAuth 2.0 Protocol Draft.
+2. **Obtain an access token:** If the user's credentials were entered correctly, the third-party client can obtain an access token. Once this token is received, it can be used to access the user's resources until the token expires or the user revokes it on the IBM Video Streaming website.
+3. **Access the user's resources:** The client can use Ustream's REST API or the IBM Video Streaming Broadcasting Library to access the user's resources (data) or to broadcast to the user's channel. The client authorizes itself using the access token, with methods described by the OAuth 2.0 Protocol Draft.
 
 ### Authorization Flows
 The OAuth 2.0 protocol provides several flows (workflows) for the first two phases. It depends on the type and architecture of the client which flow is the most suitable. The following flows are supported:
@@ -15,21 +15,20 @@ The OAuth 2.0 protocol provides several flows (workflows) for the first two phas
 * **Authorization code flow:** Suitable for third-party websites which contain a client and a server component. The user enters its credentials to a secure login webpage. After logging in, the browser is redirected to a special URL (defined by the client), passing an authorization code in the URL. The third-party server obtains the access token with another HTTP request in the background, using the authorization code. This method is more secure than the implicit flow if the third-party client has a client+server model. See the OAuth2 Draft for details.
 
 ### Endpoints
-The webpages and HTTP services invoked in during this authorization process are called Endpoints. IBM Cloud Video has the following endpoints:
+The webpages and HTTP services invoked in during this authorization process are called Endpoints. IBM Video Streaming has the following endpoints:
 
 * **Authorization endpoint:** this is the webpage where the user enters his/her credentials.
 * **Token endpoint:** this is the HTTP service where the access token can be obtained in an authorization code flow (when using the implicit flow, the access token can be obtained directly from the authorization endpoint).
 
 ### Access tokens
-There are two types of access tokens: **Bearer tokens** and **MAC tokens.** They are equivalent in the sense that they can access the same resources on the IBM Cloud Video REST API. The difference is that while bearer tokens can be only used on encrypted channels (HTTPS), MAC tokens are suitable on non-encrypted channels as well.
+There are two types of access tokens: **Bearer tokens** and **MAC tokens.** They are equivalent in the sense that they can access the same resources on the IBM Video Streaming REST API. The difference is that while bearer tokens can be only used on encrypted channels (HTTPS), MAC tokens are suitable on non-encrypted channels as well.
 
-If the client uses the IBM Cloud Video Broadcasting Library, it must use MAC tokens: the broadcasting is done on the RTMP protocol, which is unencrypted. If the client only uses the REST API, the bearer tokens are preferred because their usage is very simple and lightweight.
+If the client uses the IBM Video Streaming Broadcasting Library, it must use MAC tokens: the broadcasting is done on the RTMP protocol, which is unencrypted. If the client only uses the REST API, the bearer tokens are preferred because their usage is very simple and lightweight.
 
 Bearer tokens and MAC tokens can be obtained in the same way: the authorization endpoint has a token type parameter, so the client can specify what kind of token it wants to create.
 
 ### Token scopes, expiration
-By default, access tokens have a limited lifetime (they expire in a day) and can access only a limited amount of resources. In the authorization process the client can request extra permissions (scopes) from the user to overcome these limitations. These requests are shown to the user on the authorization endpoint. IBM Cloud Video currently supports the following scopes:
+By default, access tokens have a limited lifetime (they expire in a day) and can access only a limited amount of resources. In the authorization process the client can request extra permissions (scopes) from the user to overcome these limitations. These requests are shown to the user on the authorization endpoint. IBM Video Streaming currently supports the following scopes:
 
 * **Offline scope:** If this scope is enabled, the access token never expires.
-* **Broadcaster scope:** If this Scope is enabled, the access token can be used for broadcasting with the IBM Cloud Video Broadcasting Library. This scope are enabled only for MAC tokens.
- 
+* **Broadcaster scope:** If this Scope is enabled, the access token can be used for broadcasting with the IBM Video Streaming Broadcasting Library. This scope are enabled only for MAC tokens.

README.md

@@ -1,4 +1,4 @@
-IBM Cloud Video Enterprise Channel API Documentation
+IBM Video Streaming Enterprise Channel API Documentation
 =======
 
 https://developers.video.ibm.com/

_posts/2015-09-01-getting-started.html

@@ -6,22 +6,22 @@
 categoryItemType: documentation
 categoryItemIsShown: 1
 categoryItemWidth: 12
-categoryItemDescription: IBM Cloud Video allows third-party clients to access IBM Cloud Video users' resources (data) via a HTTP-based (RESTful) API. It also provides a Broadcaster Library that is capable of broadcasting to a user's channel. Both the REST API and the Broadcaster Library uses the OAuth 2.0 protocol for authentication and authorization.
+categoryItemDescription: IBM Video Streaming allows third-party clients to access IBM Video Streaming users' resources (data) via a HTTP-based (RESTful) API. It also provides a Broadcaster Library that is capable of broadcasting to a user's channel. Both the REST API and the Broadcaster Library uses the OAuth 2.0 protocol for authentication and authorization.
 categoryItemLabel: Read the documentation
 ---     
         <article data-sidenav="sidenav">
             <section>
                 <h2>Overview</h2>
-                <p>IBM Cloud Video allows third-party clients to access IBM Cloud Video users&#39; resources (data) via a HTTP-based (RESTful) API. It also provides a Broadcaster Library that is capable of broadcasting to a user&#39;s channel. Both the REST API and the Broadcaster Library uses the OAuth 2.0 protocol for authentication and authorization.</p>
+                <p>IBM Video Streaming allows third-party clients to access IBM Video Streaming users&#39; resources (data) via a HTTP-based (RESTful) API. It also provides a Broadcaster Library that is capable of broadcasting to a user&#39;s channel. Both the REST API and the Broadcaster Library uses the OAuth 2.0 protocol for authentication and authorization.</p>
 
 
 
                 <h3>Basic workflow</h3>
                 <p>The basic workflow of a third-party Client is the following:</p>
                 <ol>
                     <li><strong>Authorize the user:</strong> Obtain and validate the user&#39;s credentials (username and password). The client must never store these credentials, only pass it to the server for authorization.</li>
-                    <li><strong>Obtain an access token:</strong> If the user&#39;s credentials were entered correctly, the third-party client can obtain an access token. Once this token is received, it can be used to access the user&#39;s resources until the token expires or the user revokes it on the IBM Cloud Video website.</li>
-                    <li><strong>Access the user&#39;s resources:</strong> The client can use Ustream&#39;s REST API or the IBM Cloud Video Broadcasting Library to access the user&#39;s resources (data) or to broadcast to the user&#39;s channel. The client authorizes itself using the access token, with methods described by the OAuth 2.0 Protocol Draft.</li>
+                    <li><strong>Obtain an access token:</strong> If the user&#39;s credentials were entered correctly, the third-party client can obtain an access token. Once this token is received, it can be used to access the user&#39;s resources until the token expires or the user revokes it on the IBM Video Streaming website.</li>
+                    <li><strong>Access the user&#39;s resources:</strong> The client can use Ustream&#39;s REST API or the IBM Video Streaming Broadcasting Library to access the user&#39;s resources (data) or to broadcast to the user&#39;s channel. The client authorizes itself using the access token, with methods described by the OAuth 2.0 Protocol Draft.</li>
                 </ol>
 
 
@@ -37,7 +37,7 @@ <h3>Authorization Flows</h3>
 
 
                 <h3>Endpoints</h3>
-                <p>The webpages and HTTP services invoked in during this authorization process are called endpoints. IBM Cloud Video has the following endpoints:</p>
+                <p>The webpages and HTTP services invoked in during this authorization process are called endpoints. IBM Video Streaming has the following endpoints:</p>
                 <ul>
                     <li><strong>Authorization endpoint:</strong> this is the webpage where the user enters his/her credentials.</li>
                     <li><strong>Token endpoint:</strong> this is the HTTP service where the access token can be obtained in an authorization code flow (when using the implicit flow, the access token can be obtained directly from the authorization endpoint).</li>
@@ -46,16 +46,16 @@ <h3>Endpoints</h3>
 
 
                 <h3>Access tokens</h3>
-                <p>There are two types of access tokens: <strong>Bearer tokens</strong> and <strong>MAC tokens.</strong> They are equivalent in the sense that they can access the same resources on the IBM Cloud Video REST API. The difference is that while bearer tokens can be only used on encrypted channels (HTTPS), MAC tokens are suitable on non-encrypted channels as well.</p>
-                <p>If the client uses the IBM Cloud Video Broadcasting Library, it must use MAC tokens: the broadcasting is done on the RTMP protocol, which is unencrypted. If the client only uses the REST API, the bearer tokens are preferred because their usage is very simple and lightweight.</p>
+                <p>There are two types of access tokens: <strong>Bearer tokens</strong> and <strong>MAC tokens.</strong> They are equivalent in the sense that they can access the same resources on the IBM Video Streaming REST API. The difference is that while bearer tokens can be only used on encrypted channels (HTTPS), MAC tokens are suitable on non-encrypted channels as well.</p>
+                <p>If the client uses the IBM Video Streaming Broadcasting Library, it must use MAC tokens: the broadcasting is done on the RTMP protocol, which is unencrypted. If the client only uses the REST API, the bearer tokens are preferred because their usage is very simple and lightweight.</p>
                 <p>Bearer tokens and MAC tokens can be obtained in the same way: the authorization endpoint has a token type parameter, so the client can specify what kind of token it wants to create.</p>
 
 
 
                 <h3>Token scopes, expiration</h3>
-                <p>By default, access tokens have a limited lifetime (they expire in a day) and can access only a limited amount of resources. In the authorization process the client can request extra permissions (scopes) from the user to overcome these limitations. These requests are shown to the user on the authorization endpoint. IBM Cloud Video currently supports the following scope:</p>
+                <p>By default, access tokens have a limited lifetime (they expire in a day) and can access only a limited amount of resources. In the authorization process the client can request extra permissions (scopes) from the user to overcome these limitations. These requests are shown to the user on the authorization endpoint. IBM Video Streaming currently supports the following scope:</p>
                 <ul>
-                    <li><strong>Broadcaster scope:</strong> If this scope is enabled, the access token can be used for broadcasting with the IBM Cloud Video Broadcasting Library. This scope can only be used with MAC tokens.</li>
+                    <li><strong>Broadcaster scope:</strong> If this scope is enabled, the access token can be used for broadcasting with the IBM Video Streaming Broadcasting Library. This scope can only be used with MAC tokens.</li>
                 </ul>
             </section>
 
@@ -120,7 +120,7 @@ <h6>Supported OAuth 2.0 standard parameters</h6>
                     </tr>
                 </table>
 
-                <h6>IBM Cloud Video specific extra parameters</h6>
+                <h6>IBM Video Streaming specific extra parameters</h6>
                 <table class="table responsive">
                     <tr>
                         <th>parameter</th>
@@ -138,7 +138,7 @@ <h6>IBM Cloud Video specific extra parameters</h6>
                         <td><strong>device_name</strong></td>
                         <td>string</td>
                         <td>OPTIONAL</td>
-                        <td>Full product name of the Client device or application. It is used for easy identification of the OAuth2 Token. The User will be able to review which Clients are connected to his/her account, and revoke these grants on the IBM Cloud Video website.</td>
+                        <td>Full product name of the Client device or application. It is used for easy identification of the OAuth2 Token. The User will be able to review which Clients are connected to his/her account, and revoke these grants on the IBM Video Streaming website.</td>
                     </tr>
                     <tr>
                         <td><strong>display</strong></td>
@@ -204,19 +204,19 @@ <h6>Result</h6>
                     </tr>
                     <tr>
                         <td><strong>access_token</strong></td>
-                        <td>Access Token (40 character length, hexa encoded sha1 hash). Referred as <em>macId</em> in the IBM Cloud Video Broadcaster Library.</td>
+                        <td>Access Token (40 character length, hexa encoded sha1 hash). Referred as <em>macId</em> in the IBM Video Streaming Broadcaster Library.</td>
                     </tr>
                     <tr>
                         <td><strong>expires_in</strong></td>
                         <td>The current lifetime of the token in seconds.</td>
                     </tr>
                     <tr>
                         <td><strong>mac_key</strong></td>
-                        <td>MAC secret (40 character length, hexa encoded sha1 hash). Referred as <em>macSecret</em> in the IBM Cloud Video Broadcaster Library.</td>
+                        <td>MAC secret (40 character length, hexa encoded sha1 hash). Referred as <em>macSecret</em> in the IBM Video Streaming Broadcaster Library.</td>
                     </tr>
                     <tr>
                         <td><strong>created_at</strong></td>
-                        <td>UTC timestamp of the creation datetime. Referred as <em>macIssueTime</em> in the IBM Cloud Video Broadcaster Library.</td>
+                        <td>UTC timestamp of the creation datetime. Referred as <em>macIssueTime</em> in the IBM Video Streaming Broadcaster Library.</td>
                     </tr>
                     <tr>
                         <td><strong>mac_algorithm</strong></td>
@@ -356,13 +356,13 @@ <h3>Resource Owner Password Credentials flow</h3>
                         <td><strong>username</strong></td>
                         <td>string</td>
                         <td>REQUIRED</td>
-                        <td>IBM Cloud Video username</td>
+                        <td>IBM Video Streaming username</td>
                     </tr>
                     <tr>
                         <td><strong>password</strong></td>
                         <td>string</td>
                         <td>REQUIRED</td>
-                        <td>IBM Cloud Video password</td>
+                        <td>IBM Video Streaming password</td>
                     </tr>
                     <tr>
                         <td><strong>device_name</strong></td>
@@ -407,11 +407,11 @@ <h6>Response</h6>
                     </tr>
                     <tr>
                         <td><strong>mac_key</strong></td>
-                        <td>MAC secret (40 character length, hexa encoded sha1 hash). Referred as macSecret in the IBM Cloud Video Broadcaster Library.</td>
+                        <td>MAC secret (40 character length, hexa encoded sha1 hash). Referred as macSecret in the IBM Video Streaming Broadcaster Library.</td>
                     </tr>
                     <tr>
                         <td><strong>created_at</strong></td>
-                        <td>UTC timestamp of the creation datetime. Referred as macIssueTime in the IBM Cloud Video Broadcaster Library.</td>
+                        <td>UTC timestamp of the creation datetime. Referred as macIssueTime in the IBM Video Streaming Broadcaster Library.</td>
                     </tr>
                     <tr>
                         <td><strong>mac_algorithm</strong></td>
@@ -484,11 +484,11 @@ <h6>Response</h6>
                     </tr>
                     <tr>
                         <td><strong>mac_key</strong></td>
-                        <td>MAC tokens only: MAC secret (40 character length, hexa encoded sha1 hash). Referred as macSecret in the IBM Cloud Video Broadcaster Library.</td>
+                        <td>MAC tokens only: MAC secret (40 character length, hexa encoded sha1 hash). Referred as macSecret in the IBM Video Streaming Broadcaster Library.</td>
                     </tr>
                     <tr>
                         <td><strong>created_at</strong></td>
-                        <td>UTC timestamp of the creation datetime. Referred as macIssueTime in the IBM Cloud Video Broadcaster Library.</td>
+                        <td>UTC timestamp of the creation datetime. Referred as macIssueTime in the IBM Video Streaming Broadcaster Library.</td>
                     </tr>
                     <tr>
                         <td><strong>mac_algorithm</strong></td>
@@ -655,4 +655,4 @@ <h3>Creating a channel (POST)</h3>
 {"channel":{"id":"13091307","title":"Whatever Test 1234","url":"whatever-test-1234","tiny_url":"http://ustre.am/SVE7"}}
 </code></pre>
             </section>
-        </article>
+        </article>