Merge pull request #1174 from dnlkoch/fix-styleguide

Fix styleguide

README.md

@@ -53,7 +53,7 @@ export default sldToOl;
 ```
 ## <a name="installation"></a>Installation
 
-Run 
+Run
 
 ```bash
 npm i geostyler
@@ -77,7 +77,7 @@ render() {
 
 ## <a name="geostyler-behind-the-scenes"></a>GeoStyler - Behind the Scenes
 
-Internally we are using our own style definition called `GeoStyler Style` (see [TypeScript Declaration Files](#typescript-declaration-files)), which takes the best from SLD and Mapbox. We are not trying to establish just another standard, but we need an exchange format that is flexible and highly compatible with current styling standards. **Understanding GeoStyler Style is only necessary for developers of the project, not for users!** Our style parsers all read and write from and to GeoStyler Style to keep the complexity low. As a positive side effect this lets you translate from any supported style to any other supported style. 
+Internally we are using our own style definition called `GeoStyler Style` (see [TypeScript Declaration Files](#typescript-declaration-files)), which takes the best from SLD and Mapbox. We are not trying to establish just another standard, but we need an exchange format that is flexible and highly compatible with current styling standards. **Understanding GeoStyler Style is only necessary for developers of the project, not for users!** Our style parsers all read and write from and to GeoStyler Style to keep the complexity low. As a positive side effect this lets you translate from any supported style to any other supported style.
 
 Imagine your previous project was based on QGIS and now you want to setup your own web application. With GeoStyler you can still use your QGIS styles and either save all future formats in qml as well, or you simply translate all your old styles to another format e.g. OpenLayers styles or SLD. It's simple as that!
 
@@ -87,7 +87,7 @@ With these two formats there come two interfaces.
 You can implement these interfaces to create a parser.
 Compare the list of existing parsers below.
 
-![Architecture](/docs/ComponentView.png)
+![Architecture](/docs/ComponentView.jpg)
 
 <!-- Code: https://github.com/terrestris/geostyler-demo -->
 

docs/README.md

@@ -53,7 +53,7 @@ export default sldToOl;
 ```
 ## <a name="installation"></a>Installation
 
-Run 
+Run
 
 ```bash
 npm i geostyler
@@ -77,7 +77,7 @@ render() {
 
 ## <a name="geostyler-behind-the-scenes"></a>GeoStyler - Behind the Scenes
 
-Internally we are using our own style definition called `GeoStyler Style` (see [TypeScript Declaration Files](#typescript-declaration-files)), which takes the best from SLD and Mapbox. We are not trying to establish just another standard, but we need an exchange format that is flexible and highly compatible with current styling standards. **Understanding GeoStyler Style is only necessary for developers of the project, not for users!** Our style parsers all read and write from and to GeoStyler Style to keep the complexity low. As a positive side effect this lets you translate from any supported style to any other supported style. 
+Internally we are using our own style definition called `GeoStyler Style` (see [TypeScript Declaration Files](#typescript-declaration-files)), which takes the best from SLD and Mapbox. We are not trying to establish just another standard, but we need an exchange format that is flexible and highly compatible with current styling standards. **Understanding GeoStyler Style is only necessary for developers of the project, not for users!** Our style parsers all read and write from and to GeoStyler Style to keep the complexity low. As a positive side effect this lets you translate from any supported style to any other supported style.
 
 Imagine your previous project was based on QGIS and now you want to setup your own web application. With GeoStyler you can still use your QGIS styles and either save all future formats in qml as well, or you simply translate all your old styles to another format e.g. OpenLayers styles or SLD. It's simple as that!
 
@@ -87,7 +87,7 @@ With these two formats there come two interfaces.
 You can implement these interfaces to create a parser.
 Compare the list of existing parsers below.
 
-![Architecture](./ComponentView.png)
+![Architecture](./ComponentView.jpg)
 
 <!-- Code: https://github.com/terrestris/geostyler-demo -->