Capitalize comments

Signed-off-by: Alan Cha <[email protected]>

Author: Alan-Cha

docs/tutorials/watson.md

@@ -2,12 +2,10 @@
 
 OpenAPI-to-GraphQL is a library that automatically creates GraphQL wrappers for existing REST(-like) APIs, relying on the Swagger or OpenAPI specifications of these APIs. To exemplify what OpenAPI-to-GraphQL can do, let's create a GraphQL wrapper for the [IBM Watson Language Translator API](https://www.ibm.com/watson/services/language-translator/). The Language Translator API uses machine learning capabilities to detect the language of given texts, and to translate texts to any of a number of supported languages.
 
-
 ## Video demo
 
 [![OpenAPI-to-GraphQL](../conveyor_belt.png)](https://www.youtube.com/watch?v=87ryTWc85BM "Click here to watch!")
 
-
 ## Creating a simple wrapper
 
 To create a GraphQL wrapper around the API, we use the Swagger specification of the Language Translator API available [here](https://watson-api-explorer.ng.bluemix.net/listings/language-translator-v2.json). From this specification, OpenAPI-to-GraphQL creates a GraphQL schema, consisting of the API's data types and their relations. OpenAPI-to-GraphQL also creates so-called resolve functions, which interact with the Language Translator API to resolve GraphQL queries. The schema created by OpenAPI-to-GraphQL can be exposed using web application frameworks like [Express.js](https://expressjs.com/) via the [express-graphql](https://github.com/graphql/express-graphql) middleware.
@@ -37,13 +35,12 @@ async function startServer () {
   app.listen(3000)
 }
 
-// kick things off:
+// Kick things off:
 startServer()
 ```
 
 Pretty simple, no?
 
-
 ## Trying out the GraphQL wrapper
 
 Running the above code exposes the created GraphQL wrapper at `localhost:3000`. Visiting `localhost:3000/graphiql`, the well-known GraphiQL in-browser IDE for GraphQL is exposed and allows us to perform first queries, for example to identify the language of a given text:
@@ -52,7 +49,6 @@ Running the above code exposes the created GraphQL wrapper at `localhost:3000`.
 
 Note the `viewerBasicAuth` type at the root of this query. It was created by OpenAPI-to-GraphQL as a mechanism for users to provide their [Language Translator API credentials](https://www.ibm.com/watson/developercloud/language-translator/api/v2/curl.html?curl#authentication) as part of the query. If desired, OpenAPI-to-GraphQL can alternatively be configured to send credentials without the user having to explicitly state them. As we can see, the above query returns a list of identified candidate languages of the given text, which are ranked by a confidence score.
 
-
 ## Enabling nested queries
 
 Running simple queries like this one via GraphQL already provides some benefits, because the user can select the specific data _fields_ to be returned, allowing to reduce response sizes. However, arguably, much more value results from GraphQL's ability to perform more complex, nested queries. To enable nested queries, OpenAPI-to-GraphQL makes use of [links](https://swagger.io/docs/specification/links/), a new feature of the OpenAPI Specification 3.0. Links allow to define dependencies between API operations by specifying how data returned by one operation can be used as input to another operation. If present in a given OpenAPI Specification, OpenAPI-to-GraphQL uses links to enrich GraphQL types, allowing deeply nested queries.

packages/openapi-to-graphql-cli/.prettierignore

@@ -1 +1,2 @@
-lib/
+lib/
+*.md

packages/openapi-to-graphql-cli/lib/openapi-to-graphql.js

@@ -167,7 +167,7 @@ function startGraphQLServer(oas, port) {
     .then(({ schema, report }) => {
       console.log(JSON.stringify(report, null, 2))
 
-      // save local file if required
+      // Save local file if required
       if (program.save) {
         writeSchema(schema)
       } else {
@@ -176,7 +176,7 @@ function startGraphQLServer(oas, port) {
           app.use(cors())
         }
 
-        // mounting graphql endpoint using the middleware express-graphql
+        // Mounting graphql endpoint using the middleware express-graphql
         app.use(
           '/graphql',
           graphqlHTTP({
@@ -185,7 +185,7 @@ function startGraphQLServer(oas, port) {
           })
         )
 
-        // initiating the server on the port specified by user or the default one
+        // Initiating the server on the port specified by user or the default one
         app.listen(port, () => {
           console.log(`GraphQL accessible at: http://localhost:${port}/graphql`)
         })

packages/openapi-to-graphql-cli/src/openapi-to-graphql.ts

@@ -1 +1,2 @@
-lib/
+lib/
+*.md