A few documentation fixes. (#48)

- fixing plugin server location
- link to migration guide
- fixing the namespace for the Pulumi stack config

Author: ringods

docs/_index.md

@@ -9,7 +9,8 @@ The `OVH` provider must be configured with credentials to deploy and update reso
 
 ## Information
 
-Note that the [lbrlabs Pulumi OVH provider](https://github.com/lbrlabs/pulumi-ovh) is replaced by this official one.
+Note that the [lbrlabs Pulumi OVH provider](https://github.com/lbrlabs/pulumi-ovh) is replaced by this official one. See the
+[Migration Guide](./how-to-guides/migration-from-lbrlabs-package.md) for more information.
 
 ## Example
 

docs/installation-configuration.md

@@ -22,7 +22,7 @@ The Pulumi `OVH` provider is available as a package in all Pulumi languages:
 The OVH provider binary is a third party binary. It can be installed using the `pulumi plugin` command.
 
 ```bash
-pulumi plugin install resource ovh <version>
+pulumi plugin install resource ovh <version> --server api://github.com/ovh/pulumi-ovh
 ```
 
 Replace the version string with your desired version.
@@ -34,12 +34,13 @@ Your OVH credentials are never sent to pulumi.com. Pulumi uses the OVH API and t
 
 ### Get your credentials
 
-The "OVH provider" needs to be configured with a set of credentials:
+The "OVH provider" needs to be configured with a set of credentials, which can be set using
+[Pulumi stack configuration](https://www.pulumi.com/docs/concepts/config/) or environment variables:
 
-* an `endpoint` (environment variable: OVH_ENDPOINT)
-* an `applicationKey` (environment variable: OVH_APPLICATION_KEY)
-* an `applicationSecret` (environment variable: OVH_APPLICATION_SECRET)
-* a `consumerKey` (environment variable: OVH_CONSUMER_KEY)
+* `ovh:endpoint` (environment variable: `OVH_ENDPOINT`)
+* `ovh:applicationKey` (environment variable: `OVH_APPLICATION_KEY`)
+* `ovh:applicationSecret` (secret) (environment variable: `OVH_APPLICATION_SECRET`)
+* `ovh:consumerKey` (environment variable: `OVH_CONSUMER_KEY`)
 
 Why?