Skip to content

Commit c2b6e09

Browse files
committed
Revert file
1 parent 73c2d7b commit c2b6e09

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

articles/azure-maps/web-sdk-best-practices.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -217,7 +217,7 @@ If your data meets one of the following criteria, be sure to specify the min and
217217
* If the data is coming from a vector tile source, often source layers for different data types are only available through a range of zoom levels.
218218
* If using a tile layer that doesn't have tiles for all zoom levels 0 through 24 and you want it to only rendering at the levels it has tiles, and not try to fill in missing tiles with tiles from other zoom levels.
219219
* If you only want to render a layer at certain zoom levels.
220-
All layers have a `minZoom` and `maxZoom` option where the layer will be rendered when between these zoom levels based on this logic `maxZoom > zoom >= minZoom`.
220+
All layers have a `minZoom` and `maxZoom` option where the layer will be rendered when between these zoom levels based on this logic ` maxZoom > zoom >= minZoom`.
221221

222222
**Example**
223223

@@ -273,7 +273,7 @@ var layer = new atlas.layer.HeatMapLayer(source, null, {
273273
});
274274
```
275275

276-
For more information, see [Clustering and heat maps](./clustering-point-data-web-sdk.md#clustering-and-the-heat-maps-layer).
276+
Learn more in the [Clustering and heat maps in this document](clustering-point-data-web-sdk.md #clustering-and-the-heat-maps-layer)
277277

278278
### Keep image resources small
279279

0 commit comments

Comments
 (0)