Merge pull request #269367 from MeeraDi/validation-0318

v-shils · web-flow · commit aa4f5e202c35 · 2024-03-20T11:55:51.000-07:00
Bulk update: Global effort to fix validation errors
diff --git a/articles/hdinsight-aks/flink/change-data-capture-connectors-for-apache-flink.md b/articles/hdinsight-aks/flink/change-data-capture-connectors-for-apache-flink.md
@@ -28,7 +28,7 @@ The SQLServer CDC connector is a Flink source connector, which reads database sn
 
 ### Single Thread Reading
 
-The SQLServer CDC source can’t work in parallel reading, because there's only one task, which can receive change events. For more information, refer [SQLServer CDC Connector](https://ververica.github.io/flink-cdc-connectors/master/content/connectors/sqlserver-cdc.html).
+The SQLServer CDC source can’t work in parallel reading, because there's only one task, which can receive change events. For more information, refer [SQLServer CDC Connector](https://github.com/apache/flink-cdc).
 
 ### DataStream Source
 
diff --git a/articles/hdinsight-aks/flink/monitor-changes-postgres-table-flink.md b/articles/hdinsight-aks/flink/monitor-changes-postgres-table-flink.md
@@ -160,5 +160,5 @@ Now, let's learn how to monitor changes on PostgreSQL table using Flink-SQL CDC.
 ### Reference
 
 - [Apache Flink Website](https://flink.apache.org/)
-- [PostgreSQL CDC Connector](https://ververica.github.io/flink-cdc-connectors/release-2.1/content/connectors/postgres-cdc.html) is licensed under [Apache 2.0 License](https://github.com/ververica/flink-cdc-connectors/blob/master/LICENSE)
+- [PostgreSQL CDC Connector](https://github.com/apache/flink-cdc) is licensed under [Apache 2.0 License](https://github.com/ververica/flink-cdc-connectors/blob/master/LICENSE)
 - Apache, Apache Flink, Flink, and associated open source project names are [trademarks](../trademarks.md) of the [Apache Software Foundation](https://www.apache.org/) (ASF).
diff --git a/articles/hdinsight-aks/flink/sink-sql-server-table-using-flink-sql.md b/articles/hdinsight-aks/flink/sink-sql-server-table-using-flink-sql.md
@@ -170,5 +170,5 @@ Monitor the table on Flink SQL
 
 
 ###  Reference
-* [SQLServer CDC Connector](https://ververica.github.io/flink-cdc-connectors/master/content/connectors/sqlserver-cdc.html) is licensed under [Apache 2.0 License](https://github.com/ververica/flink-cdc-connectors/blob/master/LICENSE)
+* [SQLServer CDC Connector](https://github.com/apache/flink-cdc) is licensed under [Apache 2.0 License](https://github.com/ververica/flink-cdc-connectors/blob/master/LICENSE)
 * Apache, Apache Flink, Flink, and associated open source project names are [trademarks](../trademarks.md) of the [Apache Software Foundation](https://www.apache.org/) (ASF).
diff --git a/articles/openshift/howto-update-certificates.md b/articles/openshift/howto-update-certificates.md
@@ -28,4 +28,4 @@ where:
 Running this command restarts worker machines and updates the cluster certificates, setting the cluster to a known, proper state. 
 
 > [!NOTE]
-> Certificates for custom domains need to be updated manually. For more information, see the [Red Hat OpenShift documentation](https://docs.openshift.com/rosa/rosa_install_access_delete_clusters/rosa_getting_started_iam/rosa-getting-started-workflow.html).
+> Certificates for custom domains need to be updated manually. For more information, see the [Red Hat OpenShift documentation](https://docs.openshift.com).
diff --git a/articles/operator-nexus/howto-run-instance-readiness-testing.md b/articles/operator-nexus/howto-run-instance-readiness-testing.md
@@ -143,7 +143,9 @@ You can provide the network information in a `networks-blueprint.yml` file, simi
 ## One time setup
 
 ### Download IRT
-IRT is distributed via tarball from the release section of the [nexus-samples](https://aka.ms/nexus-irt) GitHub repo.
+
+IRT is distributed via tarball from the release section of the nexus-samples GitHub repo. 
+
 1. Find the release package marked with 'Latest', download it, extract it, and navigate to the `irt` directory.
 1. Extract the tarball to the local file system: `mkdir -p irt && tar xf nexus-irt.tar.gz --directory ./irt`.
 1. Switch to the new directory `cd irt`.
diff --git a/articles/sentinel/data-connectors/flare.md b/articles/sentinel/data-connectors/flare.md
@@ -18,7 +18,7 @@ ms.author: cwatson
 | --- | --- |
 | **Log Analytics table(s)** | Firework_CL<br/> |
 | **Data collection rules support** | Not currently supported |
-| **Supported by** | [Flare](https://flare.io/contact/) |
+| **Supported by** | [Flare](https://flare.io/) |
 
 ## Query samples
 
diff --git a/articles/sentinel/data-connectors/vmware-carbon-black-cloud-using-azure-functions.md b/articles/sentinel/data-connectors/vmware-carbon-black-cloud-using-azure-functions.md
@@ -17,7 +17,7 @@ The [VMware Carbon Black Cloud](https://www.vmware.com/products/carbon-black-clo
 | Connector attribute | Description |
 | --- | --- |
 | **Application settings** | apiId<br/>apiKey<br/>workspaceID<br/>workspaceKey<br/>uri<br/>timeInterval<br/>CarbonBlackOrgKey<br/>CarbonBlackLogTypes<br/>s3BucketName<br/>EventPrefixFolderName<br/>AlertPrefixFolderName<br/>AWSAccessKeyId<br/>AWSSecretAccessKey<br/>SIEMapiId (Optional)<br/>SIEMapiKey (Optional)<br/>logAnalyticsUri (optional) |
-| **Azure function app code** | https://aka.ms/sentinelcarbonblackazurefunctioncode |
+| **Azure function app code** | Download: https://aka.ms/sentinelcarbonblackazurefunctioncode |
 | **Log Analytics table(s)** | CarbonBlackEvents_CL<br/> CarbonBlackAuditLogs_CL<br/> CarbonBlackNotifications_CL<br/> |
 | **Data collection rules support** | Not currently supported |
 | **Supported by** | [Microsoft](https://support.microsoft.com/) |
@@ -87,7 +87,7 @@ To integrate with VMware Carbon Black Cloud (using Azure Functions) make sure yo
 
 Option 1 - Azure Resource Manager (ARM) Template
 
-This method provides an automated deployment of the VMware Carbon Black connector using an ARM Tempate.
+This method provides an automated deployment of the VMware Carbon Black connector using an ARM Template.
 
 1. Click the **Deploy to Azure** button below. 
 
@@ -96,7 +96,7 @@ This method provides an automated deployment of the VMware Carbon Black connecto
 3. Enter the **Workspace ID**, **Workspace Key**, **Log Types**, **API ID(s)**, **API Key(s)**, **Carbon Black Org Key**, **S3 Bucket Name**, **AWS Access Key Id**, **AWS Secret Access Key**, **EventPrefixFolderName**,**AlertPrefixFolderName**,  and validate the **URI**.
 > - Enter the URI that corresponds to your region. The complete list of API URLs can be [found here](https://community.carbonblack.com/t5/Knowledge-Base/PSC-What-URLs-are-used-to-access-the-APIs/ta-p/67346)
  - The default **Time Interval** is set to pull the last five (5) minutes of data. If the time interval needs to be modified, it is recommended to change the Function App Timer Trigger accordingly (in the function.json file, post deployment) to prevent overlapping data ingestion. 
- - Carbon Black requires a seperate set of API ID/Keys to ingest Notification alerts. Enter the SIEM API ID/Key values or leave blank, if not required. 
+ - Carbon Black requires a separate set of API ID/Keys to ingest Notification alerts. Enter the SIEM API ID/Key values or leave blank, if not required. 
 > - Note: If using Azure Key Vault secrets for any of the values above, use the`@Microsoft.KeyVault(SecretUri={Security Identifier})`schema in place of the string values. Refer to [Key Vault references documentation](/azure/app-service/app-service-key-vault-references) for further details. 
 4. Mark the checkbox labeled **I agree to the terms and conditions stated above**. 
 5. Click **Purchase** to deploy.
@@ -108,10 +108,10 @@ Use the following step-by-step instructions to deploy the VMware Carbon Black co
 
 **1. Create a Function App**
 
-1.  From the Azure Portal, navigate to [Function App](https://portal.azure.com/#blade/HubsExtension/BrowseResource/resourceType/Microsoft.Web%2Fsites/kind/functionapp), and select **+ Add**.
+1.  From the Azure portal, navigate to [Function App](https://portal.azure.com/#blade/HubsExtension/BrowseResource/resourceType/Microsoft.Web%2Fsites/kind/functionapp), and select **+ Add**.
 2. In the **Basics** tab, ensure Runtime stack is set to **Powershell Core**. 
 3. In the **Hosting** tab, ensure the **Consumption (Serverless)** plan type is selected.
-4. Make other preferrable configuration changes, if needed, then click **Create**.
+4. Make other preferable configuration changes, if needed, then click **Create**.
 
 
 **2. Import Function App Code**
@@ -120,7 +120,7 @@ Use the following step-by-step instructions to deploy the VMware Carbon Black co
 2. Select **Timer Trigger**.
 3. Enter a unique Function **Name** and modify the cron schedule, if needed. The default value is set to run the Function App every 5 minutes. (Note: the Timer trigger should match the `timeInterval` value below to prevent overlapping data), click **Create**.
 4. Click on **Code + Test** on the left pane. 
-5. Copy the [Function App Code]((https://aka.ms/sentinelcarbonblackazurefunctioncode) and paste into the Function App `run.ps1` editor.
+5. Copy the Function App Code from the downloaded - https://aka.ms/sentinelcarbonblackazurefunctioncode and paste into the Function App `run.ps1` editor.
 5. Click **Save**.
 
 
diff --git a/articles/sentinel/sentinel-solution.md b/articles/sentinel/sentinel-solution.md
@@ -13,19 +13,19 @@ ms.collection:
 
 [!INCLUDE [zero-trust-principles](../../includes/security/zero-trust-principles.md)]
 
-This article describes how to use the Microsoft Sentinel **Zero Trust (TIC 3.0)** solution, which helps governance and compliance teams monitor and respond to Zero Trust requirements according to the [TRUSTED INTERNET CONNECTIONS (TIC) 3.0](https://www.cisa.gov/tic) initiative. 
+This article describes how to use the Microsoft Sentinel **Zero Trust (TIC 3.0)** solution, which helps governance and compliance teams monitor and respond to Zero Trust requirements according to the [TRUSTED INTERNET CONNECTIONS (TIC) 3.0](https://www.cisa.gov/resources-tools/programs/trusted-internet-connections-tic) initiative. 
 
 [Microsoft Sentinel solutions](sentinel-solutions.md) are sets of bundled content, pre-configured for a specific set of data. The **Zero Trust (TIC 3.0)** solution includes a workbook, analytics rules, and a playbook, which provide an automated visualization of Zero Trust principles, cross-walked to the Trust Internet Connections framework, helping organizations to monitor configurations over time.
 
 ## The Zero Trust solution and the TIC 3.0 framework
 
-Zero Trust and TIC 3.0 are not the same, but they share many common themes and together provide a common story. The Microsoft Sentinel solution for **Zero Trust (TIC 3.0)** offers detailed crosswalks between Microsoft Sentinel and the Zero Trust model with the TIC 3.0 framework. These crosswalks help users to better understand the overlaps between the two.
+Zero Trust and TIC 3.0 aren't the same, but they share many common themes and together provide a common story. The Microsoft Sentinel solution for **Zero Trust (TIC 3.0)** offers detailed crosswalks between Microsoft Sentinel and the Zero Trust model with the TIC 3.0 framework. These crosswalks help users to better understand the overlaps between the two.
 
-While the Microsoft Sentinel solution for **Zero Trust (TIC 3.0)** provides best practice guidance, Microsoft does not guarantee nor imply compliance. All Trusted Internet Connection (TIC) requirements, validations, and controls are governed by the [Cybersecurity & Infrastructure Security Agency](https://www.cisa.gov/resources-tools/programs/trusted-internet-connections-tic).
+While the Microsoft Sentinel solution for **Zero Trust (TIC 3.0)** provides best practice guidance, Microsoft doesn't guarantee nor imply compliance. All Trusted Internet Connection (TIC) requirements, validations, and controls are governed by the [Cybersecurity & Infrastructure Security Agency](https://www.cisa.gov/resources-tools/programs/trusted-internet-connections-tic).
 
 The **Zero Trust (TIC 3.0)** solution provides visibility and situational awareness for control requirements delivered with Microsoft technologies in predominantly cloud-based environments. Customer experience will vary by user, and some panes may require additional configurations and query modification for operation.
 
-Recommendations do not imply coverage of respective controls, as they are often one of several courses of action for approaching requirements, which is unique to each customer. Recommendations should be considered a starting point for planning full or partial coverage of respective control requirements.
+Recommendations don't imply coverage of respective controls, as they're often one of several courses of action for approaching requirements, which is unique to each customer. Recommendations should be considered a starting point for planning full or partial coverage of respective control requirements.
 
 The Microsoft Sentinel solution for **Zero Trust (TIC 3.0)** is useful for any of the following users and use cases:
 
diff --git a/articles/virtual-machines/workloads/redhat/redhat-in-place-upgrade.md b/articles/virtual-machines/workloads/redhat/redhat-in-place-upgrade.md
@@ -36,7 +36,7 @@ Instructions for an in-place upgrade from Red Hat Enterprise Linux 8 VMs to Red
 Instructions for an in-place upgrade from Red Hat Enterprise Linux 7 SAP VMs to Red Hat Enterprise Linux 8 SAP VMs on Azure is provided at the [Red Hat upgrading from RHEL 7 SAP to RHEL 8 SAP documentation here.](https://access.redhat.com/solutions/5154031)
 
 ## Upgrade SAP environments from RHEL 8 VMs to RHEL 9 VMs
-Instructions for an in-place upgrade from Red Hat Enterprise Linux 8 SAP VMs to Red Hat Enterprise Linux 9 SAP VMs on Azure is provided at the [Red Hat upgrading from RHEL 8 SAP to RHEL 9 SAP documentation here.](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux_for_sap_solutions/9/html/upgrading_sap_environments_from_rhel_8_to_rhel_9/asmb_supported-upgrade-paths_how-to-in-place-upgrade-sap-environments-from-rhel8-to-rhel9)
+Instructions for an in-place upgrade from Red Hat Enterprise Linux 8 SAP VMs to Red Hat Enterprise Linux 9 SAP VMs on Azure is provided at the [Red Hat upgrading from RHEL 8 SAP to RHEL 9 SAP documentation here.](https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux_for_sap_solutions/9/html/upgrading_sap_environments_from_rhel_8_to_rhel_9/index)
 
 
 
