GITBOOK-8461: Change danger callouts to warning

Author: awileysnyk

docs/enterprise-setup/service-accounts/service-accounts-using-oauth-2.0.md

@@ -13,7 +13,7 @@ You can create an `oauth_client_secret` service account at either the Group or O
 
 The response returns the `client_secret` and the `client_id`.  You cannot view the `client_secret` again after the service account is created. If you have misplaced it, you can [rotate](manage-service-accounts-using-the-snyk-api.md#manage-a-service-account-client-secret-for-your-group) your `client_secret` and receive a new one.
 
-{% hint style="danger" %}
+{% hint style="warning" %}
 Never share the `client_secret` publicly, as this is used to authenticate your service account. Keep it secure and private.
 {% endhint %}
 

docs/enterprise-setup/snyk-broker/install-and-configure-snyk-broker/advanced-configuration-for-helm-chart-installation/insecure-downstream-mode.md

@@ -4,19 +4,18 @@ description: Usage of this mode is discouraged.
 
 # Insecure Downstream Mode
 
-In some situations, you may need to use only http for your downstream connection. Usually because of historical http only setups, these cases are relatively infrequent, and upgrading them to use https instead is our recommendations.
+In some situations, you may need to use only HTTP for your downstream connection. These cases are relatively infrequent and usually occur because of historical http-only setups. Snyk recommends upgrading to use HTTPS instead.
 
-In the cases where this is not possible in the near term, the insecure downstream mode introduces a way to force downstream requests to your SCM/JIRA/others to take place over http instead of https.
+In the cases where this is not possible in the near term, the insecure downstream mode introduces a way to force downstream requests to your SCM/JIRA/others to take place over HTTP instead of HTTPS.
 
-Using this mode should be avoided in most cases and remains opt-in.\
-It makes all requests go over http, therefore not benefiting from the safety of TLS encryption. It means all your credentials and data will appear unencrypted, which is only tolerable in tightly secure networks.
+You should avoid using this mode in most cases; it is opt-in. It makes all requests go over HTTP, thus without the benefit of the safety of TLS encryption. This mode means all your credentials and data will appear unencrypted, which is tolerable only in tightly-secured networks.
 
 Use the [Custom additional options for Broker Helm Chart installation](custom-additional-options-for-broker-helm-chart-installation.md) to inject this environment variable:
 
 `--set env[0].name=INSECURE_DOWNSTREAM --set env[0].value="true"`
 
-{% hint style="danger" %}
-Using HTTP is highly insecure ! Your data and credentials will transit in clear over the network exchanges.
+{% hint style="warning" %}
+Using HTTP is highly insecure. Your data and credentials will transit in the clear over the network exchanges.
 
-Snyk **will not be held responsible** for any credential leaks that may occur as a result of the usage this mode.
+Snyk **will not be held responsible** for any credential leaks that may occur as a result of the use of HTTP.
 {% endhint %}

docs/enterprise-setup/snyk-broker/troubleshooting-broker.md

@@ -30,7 +30,7 @@ To keep the logs concise in normal operation, Snyk produces minimal information
 
 When you set `LOG_INFO_VERBOSE="true"`, the environment variable will add the headers in these log lines without requiring that you use debug.
 
-{% hint style="danger" %}
+{% hint style="warning" %}
 If you override the default logging, some logs may be provided by other processes such as API requests, and may list credentials. Before you send any Broker logs with increased logging enabled, check for any passwords or tokens and redact them in bulk.
 {% endhint %}
 
@@ -115,20 +115,20 @@ Open Fix/Upgrade PRs or PR/recurring tests may fail because of fetching big mani
 
 ## Troubleshooting Broker with Code Agent
 
-<figure><img src="https://lh3.googleusercontent.com/r_qtONpOOEW35gdyoBcWDAiC6j04M76q8mh922SHor4bdNZdt83sj2kP7d5hbzYcWVXp4Q2hZEiCeAVOmcj4Bu1yFPdnyp3rK7kKeBK8DZEd9S133Xn3YdjddclVf5maEbP23Jor" alt="Snyk Code Analysis workflow with Broker"><figcaption><p>Snyk Code Analysis workflow with Broker</p></figcaption></figure>
+<figure><img src="https://lh3.googleusercontent.com/r_qtONpOOEW35gdyoBcWDAiC6j04M76q8mh922SHor4bdNZdt83sj2kP7d5hbzYcWVXp4Q2hZEiCeAVOmcj4Bu1yFPdnyp3rK7kKeBK8DZEd9S133Xn3YdjddclVf5maEbP23Jor" alt="&#x22;&#x22;"><figcaption><p>Snyk Code Analysis workflow with Broker</p></figcaption></figure>
 
 The best way to troubleshoot the Broker with the Code Agent is to understand the communication flow. Traffic travels from Snyk > Broker Client > Code Agent > On-premise Git > Code Agent > Snyk.
 
-The vast majority of problems with the Code aAgent are due to traffic being interrupted at one of these points.
+The vast majority of problems with the Code Agent are due to traffic being interrupted at one of these points.
 
 ### Troubleshooting the Code Agent
 
 As for Standalone Broker, in order to troubleshoot the code agent, you must generate logs. Do this by attempting to import a repository.
 
 1. Ensure that the Broker is functioning correctly and you can list the repositories. If this does not work, review the Standalone Broker troubleshooting steps.
-2. If after attempting to import a repository, you see an error message `Bundle Creation Failed`, review the logs of the containers.
+2. If, after attempting to import a repository, you see an error message `Bundle Creation Failed`, review the logs of the containers.
 3. Start with the Broker container. Run `docker logs <container id>`
-4. Look for the string `snykgit` . This is the API call from the Broker container to the Code Agent container. If you get anything other than a 200 code, there is some problem with the communication between the Broker and the Code Agent. Ensure you have the proper flags set in the docker run command. Also ensure you have set up the docker network
+4. Look for the string `snykgit` . This is the API call from the Broker container to the Code Agent container. If you get anything other than a 200 code, there is some problem with the communication between the Broker and the Code Agent. Ensure you have the proper flags set in the docker run command. Also, ensure you have set up the Docker network
 5. Review the logs of the Code Agent by running `docker logs <container id>`
 
 ### Common problems with the Code Agent

docs/implement-snyk/enterprise-implementation-guide/phase-2-configure-account/configure-snyk-apprisk-integrations.md

@@ -46,7 +46,7 @@ After you click on the Integration Hub, a list of the available integrations is
 
 Use the Snyk AppRisk Integrations Hub to configure your SCM integrations. 
 
-{% hint style="danger" %}
+{% hint style="warning" %}
 Integration Hub is a distinct integration interface dedicated to Snyk AppRisk, separate from the Organization integrations interface.
 {% endhint %}
 

docs/integrate-with-snyk/jira-and-slack-integrations/snyk-security-in-jira-cloud-integration.md

@@ -125,7 +125,7 @@ Now, according to your schedule, Jira will search for any issues for which the v
 
 ## Uninstall Snyk Security in Jira Cloud
 
-{% hint style="danger" %}
+{% hint style="warning" %}
 Uninstalling Snyk Security in Jira Cloud will disconnect Snyk vulnerabilities from their associated Jira issues.\
 \
 To uninstall a Jira app, you must be an administrator in the site-admins, administrators, or jira-administrators groups.

docs/scan-with-snyk/snyk-container/kubernetes-integration/overview-of-kubernetes-integration/how-snyk-controller-handles-your-data.md

@@ -20,6 +20,6 @@ After you install the Snyk Controller in your Kubernetes cluster, it pulls image
    * The size of scanning queues
    * The network speed.
 
-{% hint style="danger" %}
+{% hint style="warning" %}
 Snyk highly recommends NOT storing sensitive data in plain text as an environment variable in the container, for example, password, authentication token, and SSH key. Alternatively, you can store the sensitive data in a Secret, mount it as a Volume, and access the information from there.
 {% endhint %}