Skip to content

Commit 8373522

Browse files
JasonWHowellJasonWHowell
committed
Fix table headers
1 parent d06026a commit 8373522

File tree

8 files changed

+22
-35
lines changed

8 files changed

+22
-35
lines changed

‎articles/active-directory/hybrid/connect/how-to-upgrade-previous-version.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -37,7 +37,7 @@ There are a few different strategies that you can use to upgrade Azure AD Connec
3737
| Method | Description | Pros | Cons |
3838
| --- | --- | --- | --- |
3939
| [Automatic upgrade](how-to-connect-install-automatic-upgrade.md) |This is the easiest method for customers with an express installation |No manual intervention |Auto-upgrade version might not include the latest features |
40-
| [In-place upgrade](#in-place-upgrade) |If you have a single server, you can upgrade the installation in-place on the same server |Doesn't require another server |If there's an issue while in-place upgrading, you can't roll back the new release or configuration and change the active server when you are ready |Safest approach and smoother transition to a newer version. Supports Windows OS (Operating Systems) upgrade. Sync is not interrupted and doesn't impose a risk to production |Requires another server|
40+
| [In-place upgrade](#in-place-upgrade) |If you have a single server, you can upgrade the installation in-place on the same server |- Doesn't require another server<br/><br/> - Safest approach and smoother transition to a newer version. Supports Windows OS (Operating Systems) upgrade. Sync is not interrupted and doesn't impose a risk to production |- If there's an issue while in-place upgrading, you can't roll back the new release or configuration and change the active server when you are ready <br/><br/>- Requires another server|
4141

4242
For permissions information, see the [permissions required for an upgrade](reference-connect-accounts-permissions.md#upgrade).
4343

‎articles/aks/free-standard-pricing-tiers.md

Lines changed: 2 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ Azure Kubernetes Service (AKS) is now offering two pricing tiers for cluster man
2323
>
2424
> The repositioning will result in the following API changes:
2525
>
26-
> | |Prior to 2023-02-01 API|Starting from 2023-02-01 API|
26+
> | SKU |Prior to 2023-02-01 API|Starting from 2023-02-01 API|
2727
> |----------|-----------|------------|
2828
> |ManagedClusterSKUName|"Basic"|"Base"|
2929
> |ManagedClusterSKUTier|"Free" <br> "Paid"|"Free" <br> "Standard"|
@@ -83,7 +83,7 @@ Once the deployment completes, it returns JSON-formatted information about your
8383

8484
## Update the tier of an existing AKS cluster
8585

86-
The following example uses the [`az aks update`][az-aks-update] command to update the existing cluster.
86+
The following example uses the `az aks update` command to update the existing cluster.
8787

8888
```azurecli-interactive
8989
# Update an existing cluster to the Free tier
@@ -110,22 +110,8 @@ This process takes several minutes to complete. When finished, the following exa
110110
* Use [Availability Zones][availability-zones] to increase high availability with your AKS cluster workloads.
111111
* Configure your cluster to [limit egress traffic](limit-egress-traffic.md).
112112

113-
<!-- LINKS - External -->
114-
[azure-support]: https://portal.azure.com/#blade/Microsoft_Azure_Support/HelpAndSupportBlade/newsupportrequest
115-
[region-availability]: https://azure.microsoft.com/global-infrastructure/services/?products=kubernetes-service
116-
117-
<!-- LINKS - Internal -->
118-
[vm-skus]: ../virtual-machines/sizes.md
119-
[paid-sku-tier]: /rest/api/aks/managed-clusters/create-or-update#managedclusterskutier
120-
[nodepool-upgrade]: use-multiple-node-pools.md#upgrade-a-node-pool
121113
[manage-resource-group-cli]: ../azure-resource-manager/management/manage-resource-groups-cli.md
122-
[faq]: ./faq.md
123114
[availability-zones]: ./availability-zones.md
124115
[az-aks-create]: /cli/azure/aks?#az_aks_create
125-
[limit-egress-traffic]: ./limit-egress-traffic.md
126-
[az-extension-add]: /cli/azure/extension#az_extension_add
127-
[az-extension-update]: /cli/azure/extension#az_extension_update
128-
[az-aks-update]: /cli/azure/aks#az_aks_update
129-
[az-group-delete]: /cli/azure/group#az_group_delete
130116
[private-clusters]: private-clusters.md
131117
[install-azure-cli]: /cli/azure/install-azure-cli

‎articles/azure-health-insights/trial-matcher/transparency-note.md

Lines changed: 7 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -27,12 +27,13 @@ Organizations can use the Trial Matcher model to match patients to potentially s
2727

2828

2929
### Key terms
30-
| Term | What is it | | | | |
31-
|----------|--|--|--|--|--|
32-
| Patient centric | Trial Matcher, when powering a single patient trial search, helps a patient narrow down the list of potentially suitable clinical trials based on the patient’s clinical information. | |
33-
| Trial centric | Trial Matcher, when powering search for eligible patients to clinical trial, is provided with list of clinical trials (one or more) and multiple patients’ information. The model is using the matching technology to find which patients could potentially be suitable for each trial. | |
34-
| Evidence | For each trial that the model concludes the patient is not eligible for, the model returns the relevant patient information and the eligibility criteria that the model used to exclude the patient from trial eligibility. | |
35-
| Gradual matching | The model can provide patient information with gradual matching. In this mode, the user can send requests to Trial Matcher gradually, primarily via conversational intelligence or chat-like scenarios. | |
30+
31+
| Term | What is it |
32+
|----------|---------------|
33+
| Patient centric | Trial Matcher, when powering a single patient trial search, helps a patient narrow down the list of potentially suitable clinical trials based on the patient’s clinical information. |
34+
| Trial centric | Trial Matcher, when powering search for eligible patients to clinical trial, is provided with list of clinical trials (one or more) and multiple patients’ information. The model is using the matching technology to find which patients could potentially be suitable for each trial. |
35+
| Evidence | For each trial that the model concludes the patient is not eligible for, the model returns the relevant patient information and the eligibility criteria that the model used to exclude the patient from trial eligibility. |
36+
| Gradual matching | The model can provide patient information with gradual matching. In this mode, the user can send requests to Trial Matcher gradually, primarily via conversational intelligence or chat-like scenarios. |
3637

3738

3839

‎articles/azure-maps/release-notes-spatial-module.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ Stay up to date on Azure Maps:
4242
> [!div class="nextstepaction"]
4343
> [Azure Maps Blog]
4444
45-
[WmsClient.getFeatureInfoHtml]: https://learn.microsoft.com/javascript/api/azure-maps-spatial-io/atlas.io.ogc.wfsclient?view=azure-maps-typescript-latest#azure-maps-spatial-io-atlas-io-ogc-wfsclient-getfeatureinfo
45+
[WmsClient.getFeatureInfoHtml]: /javascript/api/azure-maps-spatial-io/atlas.io.ogc.wfsclient#azure-maps-spatial-io-atlas-io-ogc-wfsclient-getfeatureinfo
4646
[0.1.5]: https://www.npmjs.com/package/azure-maps-spatial-io/v/0.1.5
4747
[0.1.4]: https://www.npmjs.com/package/azure-maps-spatial-io/v/0.1.4
4848
[Azure Maps Spatial IO Samples]: https://samples.azuremaps.com/?search=Spatial%20IO%20Module

‎articles/azure-monitor/essentials/metrics-troubleshoot.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -105,7 +105,7 @@ SI uses decimal
105105

106106
IEC uses binary
107107

108-
|Value | abbreviation| IEC |Legacy| |
108+
|Value | abbreviation| IEC |Legacy| SI |
109109
|:----:|:-----------:|:---:|:----:|:---:|
110110
|1024 | Ki |kibi | K | kilo|
111111
|1024^2| Mi |mebi | M | mega|

‎articles/azure-netapp-files/performance-oracle-multiple-volumes.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -83,7 +83,7 @@ After scaling limits were tested with SLOB2, tests were conducted with a real-wo
8383

8484
This database has significant extra IO going on in addition to the application workload due to flashback being enabled and has a database block size of 16k. From the IO profile section of the AWR report, it's apparent that there is a heavy ratio of writes in comparison to reads.
8585

86-
| | Read and write per second | Read per second | Write per second |
86+
| - | Read and write per second | Read per second | Write per second |
8787
| - | -- | -- | -- |
8888
| Total (MB) | 4,988.1 | 1,395.2 | 3,592.9 |
8989

@@ -216,7 +216,7 @@ All Oracle required system configuration settings for version 19c were implement
216216
217217
The following parameters were added to the `/etc/sysctl.conf` Linux system file:
218218
* `sunrpc.max_tcp_slot_table_entries: 128`
219-
* `sunrpc.tcp_slot_table_entries = 128 `
219+
* `sunrpc.tcp_slot_table_entries = 128`
220220
221221
### Azure NetApp Files
222222
@@ -362,6 +362,6 @@ Microsoft Oracle subject matter experts have estimated that more than 80% of Ora
362362
* [Run Your Most Demanding Oracle Workloads in Azure without Sacrificing Performance or Scalability](https://techcommunity.microsoft.com/t5/azure-architecture-blog/run-your-most-demanding-oracle-workloads-in-azure-without/ba-p/3264545)
363363
* [Solution architectures using Azure NetApp Files - Oracle](azure-netapp-files-solution-architectures.md#oracle)
364364
* [Design and implement an Oracle database in Azure](../virtual-machines/workloads/oracle/oracle-design.md)
365-
* [Estimate Tool for Sizing Oracle Workloads to Azure IaaS VMs ](https://techcommunity.microsoft.com/t5/data-architecture-blog/estimate-tool-for-sizing-oracle-workloads-to-azure-iaas-vms/ba-p/1427183)
365+
* [Estimate Tool for Sizing Oracle Workloads to Azure IaaS VMs](https://techcommunity.microsoft.com/t5/data-architecture-blog/estimate-tool-for-sizing-oracle-workloads-to-azure-iaas-vms/ba-p/1427183)
366366
* [Reference architectures for Oracle Database Enterprise Edition on Azure](../virtual-machines/workloads/oracle/oracle-reference-architecture.md)
367367
* [Understand Azure NetApp Files application volumes groups for SAP HANA](application-volume-group-introduction.md)

‎articles/backup/backup-azure-reports-data-model.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -253,11 +253,11 @@ This table provides details about policy-related fields.
253253
| ScheduleWindowDuration | Integer | Recovery Services vault | Duration of the daily window in which backups can be run. Applicable for enhanced policy for Azure VM backup |
254254
| ScheduleWindowStartTime | DateTime | Recovery Services vault | Start time of the daily window in which backups can be run. Applicable for enhanced policy for Azure VM backup |
255255
| FullBackupDaysOfTheWeek | String | Backup vault | Days of the week when full backup runs. Currently applicable for Azure PostgreSQL backup |
256-
| FullBackupFrequency | String | Backup vault | Frequency of full backup. Currently applicable for Azure PostgreSQL backup | |
257-
| FullBackupTimes | String | Backup vault | Time of the day at which full backup is taken. Currently applicable for Azure PostgreSQL backup | |
256+
| FullBackupFrequency | String | Backup vault | Frequency of full backup. Currently applicable for Azure PostgreSQL backup |
257+
| FullBackupTimes | String | Backup vault | Time of the day at which full backup is taken. Currently applicable for Azure PostgreSQL backup |
258258
| IncrementalBackupDaysOfTheWeek | String | Backup vault | Days of the week when incremental backup runs. Currently applicable for Azure Disk backup |
259259
| IncrementalBackupFrequency | String | Backup vault | Frequency of incremental backup. Currently applicable for Azure Disk backup |
260-
| IncrementalBackupTimes | String | Backup vault | Time of the day at which incremental backup is taken. Currently applicable for Azure Disk backup | |
260+
| IncrementalBackupTimes | String | Backup vault | Time of the day at which incremental backup is taken. Currently applicable for Azure Disk backup |
261261
| PolicyId | String | Backup vault | Azure Resource Manager (ARM) ID of the backup policy |
262262
| SnapshotTierDailyRetentionDuration | Integer | Backup vault | Retention duration in days for daily snapshots. Applicable for Azure Blob and Azure Disk backup |
263263
| SnapshotTierWeeklyRetentionDuration | Integer | Backup vault | Retention duration in weeks for weekly snapshots. Applicable for Azure Blob and Azure Disk backup |

‎articles/ddos-protection/ddos-view-diagnostic-logs.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -120,14 +120,14 @@ The following table lists the field names and descriptions:
120120
| **ReportType** | Possible values are `Incremental` and `PostMitigation`. |
121121
| **MitigationPeriodStart** | The date and time in UTC when the mitigation started. |
122122
| **MitigationPeriodEnd** | The date and time in UTC when the mitigation ended. |
123-
| **IPAddress** | Your public IP Address. |
123+
| **IPAddress** | Your public IP Address. |
124124
| **AttackVectors** | Degradation of attack types. The keys include `TCP SYN flood`, `TCP flood`, `UDP flood`, `UDP reflection`, and `Other packet flood`. |
125-
| **TrafficOverview** | Degradation of attack traffic. The keys include `Total packets`, `Total packets dropped`, `Total TCP packets`, `Total TCP packets dropped`, `Total UDP packets`, `Total UDP packets dropped`, `Total Other packets`, and `Total Other packets dropped`. | 
126-
| **Protocols**  | Breakdown of protocols included. The keys include `TCP`, `UDP`, and `Other`.   |  
125+
| **TrafficOverview** | Degradation of attack traffic. The keys include `Total packets`, `Total packets dropped`, `Total TCP packets`, `Total TCP packets dropped`, `Total UDP packets`, `Total UDP packets dropped`, `Total Other packets`, and `Total Other packets dropped`. |
126+
| **Protocols**  | Breakdown of protocols included. The keys include `TCP`, `UDP`, and `Other`.   |
127127
| **DropReasons** | Analysis of causes of dropped packets. The keys include `Protocol violation invalid TCP`. `syn Protocol violation invalid TCP`, `Protocol violation invalid UDP`, `UDP reflection`, `TCP rate limit exceeded`, `UDP rate limit exceeded`, `Destination limit exceeded`, `Other packet flood Rate limit exceeded`, and `Packet was forwarded to service`. Protocol violation invalid drop reasons refer to malformed packets. |
128128
| **TopSourceCountries** | Breakdown of the top 10 source countries into inbound traffic. |
129129
| **TopSourceCountriesForDroppedPackets** | Analysis of the top 10 source countries for attack traffic that have been throttled. |
130-
| **TopSourceASNs** | Analysis of the top 10 sources of autonomous system numbers (ASNs) of incoming traffic.  | 
130+
| **TopSourceASNs** | Analysis of the top 10 sources of autonomous system numbers (ASNs) of incoming traffic.  |
131131
| **SourceContinents** | Analysis of the source continent for inbound traffic. |
132132
| **Type** | Type of notification. Possible values include `MitigationStarted`. `MitigationStopped`. |
133133

0 commit comments

Comments
 (0)