Skip to content
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.

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

typo: nuget -> NuGet #4921

Merged
merged 1 commit into from
Dec 17, 2018
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
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
2 changes: 1 addition & 1 deletion specification/azurestack/resource-manager/readme.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ The Azure Stack RP comprises of small services where each service has its own ta
Hence, each sub-service has its own swagger spec.

All of them are tied together using this configuration and are packaged together into one Azure Stack client library.
This makes it easier for customers to download one (nuget/npm/pip/maven/gem) Azure Stack client library package rather than installing individual packages for each sub service.
This makes it easier for customers to download one (NuGet/npm/pip/maven/gem) Azure Stack client library package rather than installing individual packages for each sub service.


---
Expand Down
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
# Cognitive Services Language SDK

The Cognitive Service Language SDK has support for the Text Analytics Cognitive Service.
While this repository contains the [Autorest](https://aka.ms/autorest) generated SDK, the easiest way to consume the SDK is by installing the Nuget package for it.
While this repository contains the [Autorest](https://aka.ms/autorest) generated SDK, the easiest way to consume the SDK is by installing the NuGet package for it.

Note that the Cognitive Services Language SDK is simply a wrapper on top of the Text Analytics Cognitive service. As such, it will generate calls to the Azure service.

Expand All @@ -11,12 +11,12 @@ You must have a [Cognitive Services API account](https://docs.microsoft.com/azur

You must also have the [endpoint and access key](../How-tos/text-analytics-how-to-access-key.md) that was generated for you during sign up.

## Installing the Nuget SDK Package
## Installing the NuGet SDK Package
1. Create a new Console solution in Visual Studio.
1. Right click on the solution and click **Manage NuGet Packages for Solution**
1. Mark the **Include Prerelease** checkbox.
1. Select the **Browse** tab, and Search for **Microsoft.Azure.CognitiveServices.Language**
1. Select the Nuget package and install it.
1. Select the NuGet package and install it.

## Calling the Text Analytics API using the SDK
The following code snippets show to consume the SDK. Note that you will need to replace `client.SubscriptionKey` with the key you received when you signed up and `client.AzureRegion` with the region you signed up for.
Expand Down
2 changes: 1 addition & 1 deletion specification/compute/resource-manager/readme.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ The compute RP comprises of small services where each service has its own tag.
Hence, each sub-service has its own swagger spec.

All of them are tied together using this configuration and are packaged together into one compute client library.
This makes it easier for customers to download one (nuget/npm/pip/maven/gem) compute client library package rather than installing individual packages for each sub service.
This makes it easier for customers to download one (NuGet/npm/pip/maven/gem) compute client library package rather than installing individual packages for each sub service.


---
Expand Down
2 changes: 1 addition & 1 deletion specification/visualstudio/resource-manager/readme.md
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ The App service RP comprises of services where each service has its own tag.
Hence, each sub-service has its own swagger spec.

All of them are tied together using this configuration and are packaged together into one compute client library.
This makes it easier for customers to download one (nuget/npm/pip/maven/gem) compute client library package rather than installing individual packages for each sub service.
This makes it easier for customers to download one (NuGet/npm/pip/maven/gem) compute client library package rather than installing individual packages for each sub service.


---
Expand Down