Merge branch 'main' into Update-F5-BIG-IP-Local-Traffic-Manager

Author: amee-sumo

docs/platform-services/automation-service/automation-service-integration-framework.md

@@ -1674,8 +1674,8 @@ Once you have saved a custom Dockerfile, the integration will be executed on a c
 
 We strongly suggest that you test your custom images as soon as you create or modify them. If by any chance you save a faulty custom Dockerfile, when the actions from that integration are triggered, their execution will fail because the Docker image will fail as well.
 
-1. To test your custom images, click where it says **TEST IMAGE** at the bottom right corner of the editor. <br/><img src={useBaseUrl('img/cloud-soar/integration-framework-test-docker-image.png')} alt="Test Docker image" width="6700"/> <br/>The system will try to build an image from your Dockerfile. While this happens, a spinner will appear in the editor. Consider this may take a few moments, depending on the instructions used in your Dockerfile. <br/><img src={useBaseUrl('img/cloud-soar/integration-framework-test-docker-image-2.png')} alt="Docker image tested" width="700"/>
-1. If your custom Docker image was built without error, a success message will pop up in your screen. Otherwise, if a proper image cannot be built from your custom Dockerfile, an error message will pop up, containing details on what went wrong. In that case, it is very important that you correct your Dockerfile and test it again until an image is built successfully. As an alternative, you can always revert to the original Docker image used by the integration, by clicking on Reset Default Image at the bottom of the editor.
+1. To test your custom images, click where it says **TEST IMAGE** at the bottom right corner of the editor. <br/><img src={useBaseUrl('img/cloud-soar/integration-framework-test-docker-image.png')} alt="Test Docker image" width="6700"/> <br/>The system will try to build an image from your Dockerfile. While this happens, a spinner will appear in the editor. Consider this may take a few moments, depending on the instructions used in your Dockerfile. <br/><img src={useBaseUrl('img/cloud-soar/integration-framework-test-docker-image-1.png')} alt="Docker image tested" width="700"/>
+1. If your custom Docker image was built without error, a success message will pop up in your screen. Otherwise, if a proper image cannot be built from your custom Dockerfile, an error message will pop up, containing details on what went wrong. In that case, it is very important that you correct your Dockerfile and test it again until an image is built successfully. As an alternative, you can always revert to the original Docker image used by the integration, by clicking on Reset Default Image at the bottom of the editor. <br/><img src={useBaseUrl('img/cloud-soar/integration-framework-test-docker-image-2.png')} alt="Docker image tested" width="700"/>
 
 ### Deleting your custom Docker image and reverting to the original one
 

docs/platform-services/threat-intelligence-indicators.md

@@ -101,7 +101,7 @@ You can also add threat intelligence indicators using the API or a collector. Se
 1. Select the format of the file to be uploaded:
     * **Normalized JSON**. A normalized JSON file.
     * **CSV**. A comma-separated value (CSV) file.
-    * **STIX 2.x JSON**. A JSON file in STIX 2.x format. When choosing this format, you must enter the name of the source in the **Source** field provided.
+    <!--* **STIX 2.x JSON**. A JSON file in STIX 2.x format. When choosing this format, you must enter the name of the source in the **Source** field provided.-->
 
    See [Upload formats](#upload-formats) for the format to use in the file.
 1. Click **Upload** to upload the file.
@@ -499,7 +499,7 @@ Also note that if your STIX file includes lines like these at the top...
 
 
 #### Example files
-
+<!--
 ##### Upload with the UI
 
 Following is an example threat indicator file in STIX 2.1 JSON format if you're uploading a file with the UI.
@@ -556,7 +556,7 @@ If you are uploading via the UI, do not include the `source` value in the file,
  ```
 
 ##### Upload with the API
-
+-->
 Following is an example threat indicator file in STIX 2.1 JSON format if you're uploading a file with the API.
 
 As shown in the following example, if uploading via the API you must add the `source` attribute outside of the indicators object, since the source is not part of the STIX standard. You must also include an `indicators` array field. (For another example for uploading via the API, see the [uploadStixIndicators API](https://api.sumologic.com/docs/#operation/uploadStixIndicators)).