address jose's comments

Author: iscai-msft

Diff for: docs/client/initializing.md

@@ -22,9 +22,7 @@ Next, on to initialization. Your constructor can take any number of parameters.
 ```js
 import { PetsClient } from "@azure/pets";
 
-let client: PetsClient;
-
-client = new PetsClient();
+const client: PetsClient = new PetsClient();
 ```
 
 If you generate with flag `--add-credentials`, your client wil be generated with an [Azure Active Directory (AAD) token credential][aad_authentication]. We always recommend
@@ -37,9 +35,7 @@ As an installation note, the [`@azure/identity`][azure_identity_library] library
 import { DefaultAzureCredential } from "@azure/identity";
 import { PetsClient } from "@azure/pets";
 
-let client: PetsClient;
-
-client = new PetsClient(new DefaultAzureCredential());
+const client: PetsClient = new PetsClient(new DefaultAzureCredential());
 ```
 
 <!-- LINKS -->

Diff for: docs/client/models.md

@@ -2,19 +2,17 @@
 
 ## General
 
-Models and enums are generated in the `models` namespace. So, say you are using package `@azure/pets`. To access model `Dog`, you would use the following code
+Models and enums are generated in the `models` module. So, say you are using package `@azure/pets`. To access model `Dog`, you would use the following code
 snippet
 
 ```js
-import { Dog } from "@azure/pets.models";
+import { Dog } from "@azure/pets";
 ```
 
 Enums are also listed in the `models` namespace, so say you have enum class `DogTypes`. To access the `Dalmation` enum, your code would look like
 
 ```js
-import { DogTypes } from "@azure/pets.models";
+import { DogTypes } from "@azure/pets";
 
-let dogType: str;
-
-dogType = DogTypes.Dalmation;
+const dogType: str = DogTypes.Dalmation;
 ```

Diff for: docs/client/operations.md

@@ -1,6 +1,6 @@
 # <img align="center" src="../images/logo.png">  Calling Operations with Your Typescript Client
 
-AutoRest provides both synchronous and asynchronous method overloads for each service operation.
+AutoRest provides asynchronous method overloads for each service operation.
 Depending on your swagger definition, operations can be accessed through operation groups (TODO: link to swagger docs) on the client,
 or directly on the client.
 
@@ -14,22 +14,13 @@ itself, i.e. `client.getDog()`.
 
 ## Regular Operations
 
-### Sync Operations
-
-We don't generate sync operations, all of our operations are async.
-
-### Async Operations
-
-When calling our async operations, we use our async client, which is in a different module. Following the [example above](#sync-operations Sync Operations),
-our call to `getDog` looks like this:
+When calling our async operations, we go through our client
 
 ```js
 import { DefaultAzureCredential } from "@azure/identity";
 import { PetsClient } from "@azure/pets";
 
-let client: PetsClient;
-
-client = new PetsClient(new DefaultAzureCredential());
+const client: PetsClient = new PetsClient(new DefaultAzureCredential());
 const dog = await client.getDog();
 ```
 
@@ -41,25 +32,16 @@ In concurrence with our [typescript guidelines][poller_guidelines], all of our l
 
 For our example, we will use the long running operation generated from [this][example_swagger] swagger. Let's say we generated this swagger with package name `@azure/lro`.
 
-### Sync Long Running Operations
-
-We don't generate sync operations, all of our operations are async.
-
-### Async Long Running Operations
-
 By default, our async long running operations return an [`Poller`][poller] polling object, though there [are ways][custom_poller] of changing this. Calling `.pollUntilDone()`
 on the poller will wait until the long running operation finishes then return the final result.
 
 ```js
 import { DefaultAzureCredential } from "@azure/identity";
 import { Product, PollingPagingExampleClient } from "@azure/lro";
 
-let client: PollingPagingExampleClient;
-let inputProduct: Product;
-
-client = new PollingPagingExampleClient(new DefaultAzureCredential());
+const client: PollingPagingExampleClient = new PollingPagingExampleClient(new DefaultAzureCredential());
 
-inputProduct = {
+const inputProduct: Product = {
     id: 1;
     name: "My Polling example"
 };
@@ -75,23 +57,15 @@ is initially called.
 
 For our example, we will use the long running operation generated from [this][example_swagger] swagger. Let's say we generated this swagger with package name `@azure/paging`.
 
-### Sync Paging Operations
-
-We don't generate sync operations, all of our operations are async.
-
-### Async Paging Operations
-
-By default, our sync paging operations return an [`PagedAsyncIterableIterator`][paged_async_iterable_iterator] pager. Since network calls aren't
+By default, our async paging operations return an [`PagedAsyncIterableIterator`][paged_async_iterable_iterator] pager. Since network calls aren't
 made until starting to page, our generated operation is synchronous, and there's no need to wait the initial call to the function. Since network calls are made when iterating,
 we have to do async looping.
 
 ```js
 import { DefaultAzureCredential } from "@azure/identity";
 import { PollingPagingExampleClient } from "@azure/paging";
 
-let client: PollingPagingExampleClient;
-
-client = new PollingPagingExampleClient(new DefaultAzureCredential());
+const client: PollingPagingExampleClient = new PollingPagingExampleClient(new DefaultAzureCredential());
 
 const pager = client.basicPaging();
 for await (const product of pager) {

Diff for: docs/client/tracing.md

@@ -18,13 +18,13 @@ Since there is no explicit context you need to pass, you can create your usual O
 The following example uses the [Zipkin][zipkin] exporter.
 
 ```js
-const tracing = require("@opencensus/nodejs");
-const { ZipkinTraceExporter } = require("@opencensus/exporter-zipkin");
-const {
+import tracing from "@opencensus/nodejs");
+import { ZipkinTraceExporter } from "@opencensus/exporter-zipkin";
+import {
   setTracer,
   OpenCensusTracerWrapper,
   OpenCensusSpanWrapper
-} = require("@azure/core-tracing");
+} from "@azure/core-tracing";
 
 const tracer = tracing.start({ samplingRate: 1 }).tracer;
 
@@ -46,17 +46,17 @@ tracer.startRootSpan({ name: "root" }, async (rootSpanEx) => {
 
 First step is to install our [`OpenTelemetry` library][our_open_telemetry_library]:
 
-```python
-pip install azure-core-tracing-opentelemetry
+```bash
+npm install --save @azure/core-tracing
 ```
 
 Since there is no explicit context you need to pass, you can create your usual OpenTelemetry tracer and call the generated SDKs.
 The following example uses the [Zipkin][zipkin] exporter.
 ```js
-const opentelemetry = require("@opentelemetry/core");
-const { BasicTracer, SimpleSpanProcessor } = require("@opentelemetry/tracing");
-const { ZipkinExporter } = require("@opentelemetry/exporter-zipkin");
-const { setTracer } = require("@azure/core-tracing");
+import opentelemetry from "@opentelemetry/core";
+import { BasicTracer, SimpleSpanProcessor } from "@opentelemetry/tracing";
+import { ZipkinExporter } = from "@opentelemetry/exporter-zipkin";
+import { setTracer } from "@azure/core-tracing";
 
 const exporter = new ZipkinExporter({
   serviceName: "azure-tracing-sample"

Diff for: docs/client/troubleshooting.md

@@ -10,9 +10,7 @@ A very basic form of error handling looks like this
 import { DefaultAzureCredential } from "@azure/identity";
 import { PetsClient } from "@azure/pets";
 
-let client: PetsClient;
-
-client = new PetsClient(new DefaultAzureCredential());
+const client: PetsClient = new PetsClient(new DefaultAzureCredential());
 try {
     const dog = await client.getDog();
 } catch (err) {

Diff for: docs/faq.md

@@ -2,7 +2,7 @@
 
 1. What version of AutoRest Typescript should I use?
 
-    CURRENTLY NO AUTOREST TYPESCRIPT ION NPM
+    CURRENTLY NO AUTOREST TYPESCRIPT ON NPM
 
     We highly recommend you use the latest AutoRest Typescript version published to [npm][autorest_npm]. The latest version
     is the default if you use flag `--typescript`, though you may need to run an `autorest --reset` if it seems

Diff for: docs/readme.md

@@ -2,7 +2,6 @@
 
 These documents are Typescript-specific, see [our main docs][main_docs] for more general information
 
-
 1. Generating Typescript Clients with AutoRest
     - How do I generate code? Main documents are [here][main_generate], while here are the [typescript-specific docs][typescript_generate]