ci(validate.yml): fix typo to match config file

.github/workflows/validate.yml

@@ -32,7 +32,7 @@ jobs:
       with:
         args: zip -qr felixrelleum-geomapwms-panel.zip felixrelleum-geomapwms-panel
     - name: Run validator
-      run: npx --yes @grafana/plugin-validator@latest -config ./plugin-validator-config.yaml -sourceCodeUri file://. felixrelleum-geomapwms-panel.zip # https://github.com/grafana/plugin-validator
+      run: npx --yes @grafana/plugin-validator@latest -config ./plugin-validator-config.yml -sourceCodeUri file://. felixrelleum-geomapwms-panel.zip # https://github.com/grafana/plugin-validator
     - name: Clean up
       run: rm -r felixrelleum-geomapwms-panel.zip
 

README.md

@@ -44,7 +44,7 @@ Layer names:
 
 ![](https://raw.githubusercontent.com/felix-mu/geomap-wms-panel/main/mutli-layer-whitespaces.PNG)
 
-## ⚠️ Troubleshooting data layers when merging to multiple datasource queries into one map layer
+## ⚠️ Troubleshooting data layers when merging multiple datasource queries into one map layer
 In some occasions it might be necessary to join mutliple datasource queries into one output dataset to summarize information coming from different sources in a single map layer. This can be achieved by applying [transformations](https://grafana.com/docs/grafana/latest/panels-visualizations/query-transform-data/transform-data/) on the returned data frames.
 
 ![alt text](https://raw.githubusercontent.com/felix-mu/geomap-wms-panel/main/multiple_queries.png)
@@ -55,15 +55,15 @@ This often results in data structure like the following which might be inspected
 
 ![alt text](https://raw.githubusercontent.com/felix-mu/geomap-wms-panel/main/dataframe_after_transformation.png)
 
-The above data structure is not compatible with Geomap Panel Plugin's query input which expects either a data frame with metadata fields like "refId" or "meta".
+The above data structure is not compatible with Geomap Panel Plugin's query input which expects a data frame with metadata fields like "refId" or "meta".
 
 ![alt text](https://raw.githubusercontent.com/felix-mu/geomap-wms-panel/main/dataframe.png)
 
 A workaround to solve this problem is to use the [prepare time series transformation](https://grafana.com/docs/grafana/latest/panels-visualizations/query-transform-data/transform-data/#prepare-time-series) with the setting _"Wide time series"_ as last transformation in the processing chain.
 
 ![alt text](https://raw.githubusercontent.com/felix-mu/geomap-wms-panel/main/preparetimeseries.png)
 
-This adds a "meta" field to the data object and therefore can now be processed by the Geomap Panel Plugin.
+The latter trasnformation a "meta" field to the data object and therefore can now be processed by the Geomap Panel Plugin.
 
 ![alt text](https://raw.githubusercontent.com/felix-mu/geomap-wms-panel/main/dataframe_final.png)