document issue and remediation, add to changelog

Author: Stacy Rendall

CHANGELOG.md

@@ -2,10 +2,11 @@
 
 ### ✨ Features and improvements
 - _...Add new stuff here..._
+- Add note regarding visual artifacts that can appear with large width/size/offset values on vector tile layers, highlight remediation options ([#4160](https://github.com/maplibre/maplibre-gl-js/issues/4160))
 
 ### 🐞 Bug fixes
 - _...Add new stuff here..._
-- 
+-
 ## 24.1.1
 
 ### 🐞 Bug fixes

build/generate-docs.ts

@@ -355,7 +355,7 @@ function createLayersContent() {
 function createSourcesContent() {
     const sourcesExtraData = {
         vector: {
-            doc: 'A vector tile source. Tiles must be in [Mapbox Vector Tile format](https://github.com/mapbox/vector-tile-spec). All geometric coordinates in vector tiles must be between \`-1 * extent\` and \`(extent * 2) - 1\` inclusive. All layers that use a vector source must specify a [`source-layer`](layers.md#source-layer) value.',
+            doc: 'A vector tile source. Tiles must be in [Mapbox Vector Tile format](https://github.com/mapbox/vector-tile-spec). All geometric coordinates in vector tiles must be between \`-1 * extent\` and \`(extent * 2) - 1\` inclusive. All layers that use a vector source must specify a [`source-layer`](layers.md#source-layer) value. Note that features are only rendered within their originating tile, which may lead to visual artifacts when large values are assigned to width, radius, size or offset properties. To mitigate rendering issues, either reduce the associated value or increase the tile buffer size during generation (for example, use [the `-b` value with Tippecanoe](https://github.com/felt/tippecanoe?tab=readme-ov-file#controlling-clipping-to-tile-boundaries) to specify a larger buffer).',
             example: {
                 'maplibre-streets': {
                     'type': 'vector',