Use named import in the Readme (#182)

* Use named import in the Readme

Named import is better practice as it will lead to smaller bundle size when used

* fix spacing

Author: petr-hajek

README.md

@@ -40,30 +40,30 @@ In addition to the details and examples provided in this readme, check out the [
 **Recommended for:** advanced applications
 
 ```ts
-import * as maptilersdk from '@maptiler/sdk';
+import { config, Map } from '@maptiler/sdk';
 
 // Add your MapTiler Cloud API key to the config
 // (Go to https://cloud.maptiler.com/account/keys/ to get one for free!)
-maptilersdk.config.apiKey = 'YOUR_API_KEY';
+config.apiKey = 'YOUR_API_KEY';
 
 // Let's say you have a DIV ready to receive a map
 const mapContainer = document.getElementById('my-container-div');
 
 // Instantiate the map
-const map = new maptilersdk.Map({
+const map = new Map({
   container: mapContainer,
 });
 ```
 
 Alternatively, the `apiKey` can be set as Map option instead of in the `config` object. Yet, this will still internally propagate to the `config` object:
 ```ts
-import * as maptilersdk from '@maptiler/sdk';
+import { Map } from '@maptiler/sdk';
 
 // Let's say you have a DIV ready to receive a map
 const mapContainer = document.getElementById('my-container-div');
 
 // Instantiate the map
-const map = new maptilersdk.Map({
+const map = new Map({
   container: mapContainer,
   apiKey: 'YOUR_API_KEY'
 });