/**
 * Flags to enable experimental features in CesiumJS. Stability and performance
 * may not be optimal when these are enabled. Experimental features are subject
 * to change without Cesium's standard deprecation policy.
 *
 * @private
 */
var ExperimentalFeatures = {
  /**
   * Toggles the usage of the ModelExperimental class.
   *
   * @type {Boolean}
   */
  enableModelExperimental: false,
};

export default ExperimentalFeatures;

@@ -50,17 +50,16 @@
 esiumJS.
- 
 Stabilit
@@ -76,16 +76,16 @@
 ormance%0A
+
  * may n
@@ -215,16 +215,727 @@
 policy.%0A
+ * %3Cp%3E%0A * Experimental features must still uphold Cesium's quality standards. Here%0A * are some guidelines:%0A * %3C/p%3E%0A * %3Cul%3E%0A *   %3Cli%3EExperimental features must have high unit test coverage like any other feature.%3C/li%3E%0A *   %3Cli%3EExperimental features are intended for large features where there is benefit of merging some of the code sooner (e.g. to avoid long-running staging branches)%3C/li%3E%0A *   %3Cli%3EExperimental flags should be short-lived. Make it clear in the PR what it would take to promote the feature to a regular feature.%3C/li%3E%0A *   %3Cli%3ETo avoid cluttering the code, check the flag in as few places as possible. Ideally this would be a single place. See %7B@link getModelClass%7D for an example.%3C/li%3E%0A * %3C/ul%3E%0A
  *%0A * @p
@@ -1040,16 +1040,16 @@
 s.%0A   *%0A
-
    * @ty
@@ -1061,16 +1061,30 @@
 oolean%7D%0A
+   * @private%0A
    */%0A  

Add more explanation to ExperimentalFeatures