Merge pull request #189322 from djrmetaswitch/apex-pre-review-fixes

Reformatting tables and removing unused images.

Author: GitHubber17

articles/private-5g-core/collect-required-information-for-a-site.md

@@ -44,9 +44,9 @@ Collect all the values in the following table to define the packet core instance
 
    |Value  |Field name in Azure portal  |
    |---------|---------|
-   |<p>The IP address for the packet core instance N2 signaling interface.</p><p>You identified this in [Allocate subnets and IP addresses](complete-private-mobile-network-prerequisites.md#allocate-subnets-and-ip-addresses) and it must match the value you used when deploying the AKS-HCI cluster.</p>                 |**N2 address (signaling)**
-   |<p>The network address of the access subnet in Classless Inter-Domain Routing (CIDR) notation.</p><p>You identified this in [Allocate subnets and IP addresses](complete-private-mobile-network-prerequisites.md#allocate-subnets-and-ip-addresses) and it must match the value you used when deploying the AKS-HCI cluster.</p>          |**N2 subnet** and **N3 subnet**|
-   |<p>The access subnet default gateway.</p><p>You identified this in [Allocate subnets and IP addresses](complete-private-mobile-network-prerequisites.md#allocate-subnets-and-ip-addresses) and it must match the value you used when deploying the AKS-HCI cluster.</p>                        |**N2 gateway** and **N3 gateway**|
+   | The IP address for the packet core instance N2 signaling interface. You identified this in [Allocate subnets and IP addresses](complete-private-mobile-network-prerequisites.md#allocate-subnets-and-ip-addresses) and it must match the value you used when deploying the AKS-HCI cluster.                 |**N2 address (signaling)**
+   | The network address of the access subnet in Classless Inter-Domain Routing (CIDR) notation. You identified this in [Allocate subnets and IP addresses](complete-private-mobile-network-prerequisites.md#allocate-subnets-and-ip-addresses) and it must match the value you used when deploying the AKS-HCI cluster.          |**N2 subnet** and **N3 subnet**|
+   | The access subnet default gateway. You identified this in [Allocate subnets and IP addresses](complete-private-mobile-network-prerequisites.md#allocate-subnets-and-ip-addresses) and it must match the value you used when deploying the AKS-HCI cluster.                        |**N2 gateway** and **N3 gateway**|
 
 ## Collect data network values
 
@@ -58,9 +58,9 @@ Collect all the values in the following table to define the packet core instance
    |Value  |Field name in Azure portal  |
    |---------|---------|
    |The name of the data network.                  |**Data network**|
-   |<p>The network address of the data subnet in CIDR notation.</p><p>You identified this in [Allocate subnets and IP addresses](complete-private-mobile-network-prerequisites.md#allocate-subnets-and-ip-addresses) and it must match the value you used when deploying the AKS-HCI cluster.</p>                  |**N6 subnet**|
-   |<p>The data subnet default gateway.</p><p>You identified this in [Allocate subnets and IP addresses](complete-private-mobile-network-prerequisites.md#allocate-subnets-and-ip-addresses) and it must match the value you used when deploying the AKS-HCI cluster.</p>                                |**N6 gateway**|
-   |<p>The network address of the subnet from which IP addresses must be allocated to User Equipment (UEs), given in CIDR notation. You identified this in [Allocate subnets and IP addresses](complete-private-mobile-network-prerequisites.md#allocate-subnets-and-ip-addresses).</p><p> The following example shows the network address format.</p><p>`198.51.100.0/24`</p><p>Note that the UE subnets aren't related to the access subnet.</p>    |**UE IP subnet**|
+   |The network address of the data subnet in CIDR notation. You identified this in [Allocate subnets and IP addresses](complete-private-mobile-network-prerequisites.md#allocate-subnets-and-ip-addresses) and it must match the value you used when deploying the AKS-HCI cluster.                  |**N6 subnet**|
+   |The data subnet default gateway. You identified this in [Allocate subnets and IP addresses](complete-private-mobile-network-prerequisites.md#allocate-subnets-and-ip-addresses) and it must match the value you used when deploying the AKS-HCI cluster.                               |**N6 gateway**|
+   | The network address of the subnet from which IP addresses must be allocated to User Equipment (UEs), given in CIDR notation. You identified this in [Allocate subnets and IP addresses](complete-private-mobile-network-prerequisites.md#allocate-subnets-and-ip-addresses). The following example shows the network address format. </br></br>`198.51.100.0/24` </br></br>Note that the UE subnets aren't related to the access subnet.    |**UE IP subnet**|
    |Whether Network Address and Port Translation (NAPT) should be enabled for this data network. NAPT allows you to translate a large pool of private IP addresses for UEs to a small number of public IP addresses. The translation is performed at the point where traffic enters the core network, maximizing the utility of a limited supply of public IP addresses.    |**NAPT**|
 
 ## Next steps

articles/private-5g-core/collect-required-information-for-service.md

@@ -32,14 +32,14 @@ Collect each of the values in the table below for your service.
 
 | Value | Azure portal field name | 
 |--|--|
-| <p>The name of the service. This name must only contain alphanumeric characters, dashes, or underscores. You also must not use any of the following reserved strings:</p><ul><li>default</li><li>requested</li><li>service</li></ul> | **Service name** |
-| <p>A precedence value that the packet core instance must use to decide between services when identifying the QoS values to offer.</p><p>This value must be an integer between 0 and 255 and must be unique among all services configured on the packet core instance. A lower value means a higher priority.</p> | **Service precedence** |
-| <p>The maximum bit rate (MBR) for uplink traffic (traveling away from user equipment (UEs)) across all SDFs that match data flow policy rules configured on this service.</p><p>The MBR must be given in the following form:</p><p>`<Quantity>` `<Unit>`</p><ul><li>`<Unit>` must be one of the following:<ul><li>*bps*</li><li>*Kbps*</li><li>*Mbps*</li><li>*Gbps*</li><li>*Tbps*</li></ul><li>`<Quantity>` is the quantity of your chosen unit.</li></ul><p>For example, `10 Mbps`.</p> | **Maximum bit rate (MBR) - Uplink** | 
-| <p>The maximum bit rate (MBR) for downlink traffic (traveling towards UEs) across all SDFs that match data flow policy rules configured on this service.</p><p>The MBR must be given in the following form:</p><p>`<Quantity>` `<Unit>`</p><ul><li>`<Unit>` must be one of the following:<ul><li>*bps*</li><li>*Kbps*</li><li>*Mbps*</li><li>*Gbps*</li><li>*Tbps*</li></ul><li>`<Quantity>` is the quantity of your chosen unit.</li></ul><p>For example, `10 Mbps`.</p> | **Maximum bit rate (MBR) - Downlink** | 
-| <p>The default QoS Flow Allocation and Retention Policy (ARP) priority level for this service. Flows with a higher ARP priority level preempt flows with a lower ARP priority level.</p><p>The ARP priority level must be an integer between 1 (highest priority) and 15 (lowest priority).</p><p>See 3GPP TS 23.501 for a full description of the ARP parameters.</p> | **Allocation and Retention Priority level** |
-| <p>The default 5G QoS Indicator (5QI) value for this service. The 5QI value identifies a set of 5G QoS characteristics that control QoS forwarding treatment for QoS Flows. See 3GPP TS 23.501 for a full description of the 5QI parameter.</p><p>We recommend you choose a 5QI value that corresponds to a non-GBR QoS Flow (as described in 3GPP TS 23.501). Non-GBR QoS Flows are in the following ranges:</p><ul><li>5-9</li><li>69-70</li><li>79-80</li></ul><p>You can also choose a non-standardized 5QI value.</p><p>Azure Private 5G Core doesn't support 5QI values corresponding GBR or delay-critical GBR QoS Flows. Don't use a value in any of the following ranges:</p><ul><li>1-4</li><li>65-67</li><li>71-76</li><li>82-85</li></ul> | **5G QoS Indicator (5QI)** |
-| <p>The default QoS Flow preemption capability for QoS Flows for this service. The preemption capability of a QoS Flow controls whether it can preempt another QoS Flow with a lower priority level.</p><p>You can choose from the following values:</p><ul><li>**May not preempt**</li><li>**May preempt**</li></ul><p>See 3GPP TS 23.501 for a full description of the ARP parameters.</p> | **Preemption capability** |
-| <p>The default QoS Flow preemption vulnerability for QoS Flows for this service. The preemption vulnerability of a QoS Flow controls whether it can be preempted another QoS Flow with a higher priority level.</p><p>You can choose from the following values:</p><ul><li>**Preemptable**</li><li>**Not preemptable**</li></ul><p>See 3GPP TS 23.501 for a full description of the ARP parameters.</p> | **Preemption vulnerability** |
+| The name of the service. This name must only contain alphanumeric characters, dashes, or underscores. You also must not use any of the following reserved strings: *default*; *requested*; *service*. | **Service name** |
+| A precedence value that the packet core instance must use to decide between services when identifying the QoS values to offer. This value must be an integer between 0 and 255 and must be unique among all services configured on the packet core instance. A lower value means a higher priority. | **Service precedence** |
+| The maximum bit rate (MBR) for uplink traffic (traveling away from user equipment (UEs)) across all SDFs that match data flow policy rules configured on this service. The MBR must be given in the following form: `<Quantity>` `<Unit>` </br></br>`<Unit>` must be one of the following: </br></br>- *bps* </br>- *Kbps* </br>- *Mbps* </br>- *Gbps* </br>- *Tbps* </br></br>`<Quantity>` is the quantity of your chosen unit. </br></br>For example, `10 Mbps`. | **Maximum bit rate (MBR) - Uplink** | 
+| The maximum bit rate (MBR) for downlink traffic (traveling towards UEs) across all SDFs that match data flow policy rules configured on this service. The MBR must be given in the following form: `<Quantity>` `<Unit>` </br></br>`<Unit>` must be one of the following: </br></br>- *bps* </br>- *Kbps* </br>- *Mbps* </br>- *Gbps* </br>- *Tbps* </br></br>`<Quantity>` is the quantity of your chosen unit. </br></br>For example, `10 Mbps`. | **Maximum bit rate (MBR) - Downlink** | 
+| The default QoS Flow Allocation and Retention Policy (ARP) priority level for this service. Flows with a higher ARP priority level preempt flows with a lower ARP priority level. The ARP priority level must be an integer between 1 (highest priority) and 15 (lowest priority). See 3GPP TS 23.501 for a full description of the ARP parameters. | **Allocation and Retention Priority level** |
+| The default 5G QoS Indicator (5QI) value for this service. The 5QI value identifies a set of 5G QoS characteristics that control QoS forwarding treatment for QoS Flows. See 3GPP TS 23.501 for a full description of the 5QI parameter. </br></br>We recommend you choose a 5QI value that corresponds to a non-GBR QoS Flow (as described in 3GPP TS 23.501). Non-GBR QoS Flows are in the following ranges: 5-9; 69-70; 79-80.</br></br>You can also choose a non-standardized 5QI value.</p><p>Azure Private 5G Core doesn't support 5QI values corresponding GBR or delay-critical GBR QoS Flows. Don't use a value in any of the following ranges: 1-4; 65-67; 71-76; 82-85. | **5G QoS Indicator (5QI)** |
+| The default QoS Flow preemption capability for QoS Flows for this service. The preemption capability of a QoS Flow controls whether it can preempt another QoS Flow with a lower priority level. You can choose from the following values: </br></br>- **May not preempt** </br>- **May preempt** </br></br>See 3GPP TS 23.501 for a full description of the ARP parameters. | **Preemption capability** |
+| The default QoS Flow preemption vulnerability for QoS Flows for this service. The preemption vulnerability of a QoS Flow controls whether it can be preempted another QoS Flow with a higher priority level. You can choose from the following values: </br></br>- **Preemptable** </br>- **Not preemptable** </br></br>See 3GPP TS 23.501 for a full description of the ARP parameters. | **Preemption vulnerability** |
 
 ## Data flow policy rule(s)
 
@@ -56,21 +56,21 @@ Collect the values in the table below for each data flow policy rule you want to
 
 | Value | Azure portal field name |
 |--|--|
-| <p>The name of the data flow policy rule. This name must only contain alphanumeric characters, dashes, or underscores. It must not match any other rule configured on the same service. You also must not use any of the following reserved strings.</p><ul><li>default</li><li>requested</li><li>service</li></ul> | **Rule name** |
-| <p>A precedence value that the packet core instance must use to decide between data flow policy rules.</p><p>This value must be an integer between 0 and 255 and must be unique among all data flow policy rules configured on the packet core instance. A lower value means a higher priority.</p> | **Policy rule precedence** |
-| <p>A traffic control setting to determine whether flows that match a data flow template on this data flow policy rule are permitted. Choose one of the following values:</p><ul><li>**Enabled** - Matching flows are permitted.</li><li>**Blocked** - Matching flows are blocked.</li> | **Traffic control** |
+| The name of the data flow policy rule. This name must only contain alphanumeric characters, dashes, or underscores. It must not match any other rule configured on the same service. You also must not use any of the following reserved strings: *default*; *requested*; *service*. | **Rule name** |
+| A precedence value that the packet core instance must use to decide between data flow policy rules. This value must be an integer between 0 and 255 and must be unique among all data flow policy rules configured on the packet core instance. A lower value means a higher priority. | **Policy rule precedence** |
+| A traffic control setting to determine whether flows that match a data flow template on this data flow policy rule are permitted. Choose one of the following values: </br></br>- **Enabled** - Matching flows are permitted. </br>- **Blocked** - Matching flows are blocked. | **Traffic control** |
 
 ### Collect data flow template values
 
 Collect the following values for each data flow template you want to use for a particular data flow policy rule.
 
 | Value | Azure portal field name |
 |--|--|
-| <p>The name of the data flow template. This name must only contain alphanumeric characters, dashes, or underscores. It must not match any other template configured on the same rule. You also must not use any of the following reserved strings:</p><ul><li>default</li><li>requested</li><li>service</li></ul> | **Template name** |
-| <p>The protocol(s) allowed for this flow.</p><ul><li>If you want to allow the flow to use any protocol within the Internet Protocol suite, you can set this field to **All**.</li><li>If you want to allow a selection of protocols, you can select them from the list displayed in the field. If a protocol isn't in the list, you can specify it by entering its corresponding IANA Assigned Internet Protocol Number, as described in the [IANA website](https://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml). For example, for IGMP, you must use 2. | **Protocols**  |
-| <p>The direction of this flow. Choose one of the following values:</p><ul><li>**Uplink** - traffic flowing away from UEs.</li><li>**Downlink** - traffic flowing towards UEs.</li><li>**Bidirectional** - traffic flowing in both directions.</li></ul> | **Direction** |
-| <p>The remote IP address(es) to which UEs will connect for this flow.</p><ul><li>If you want to allow connections on any IP address, you must use the value `any`.</li><li>Otherwise, you must provide each remote IP address or IP address range to which the packet core instance will connect for this flow. Provide these IP addresses in CIDR notation, including the netmask (for example, `192.0.2.0/24`).</li></ul><p>Provide a comma-separated list of IP addresses and IP address ranges. For example:</p><p>`192.0.2.54/32, 198.51.100.0/24`</p> | **Remote IPs** |
-| <p>The remote port(s) to which UEs will connect for this flow. You can specify one or more ports or port ranges. Port ranges must be specified as `<FirstPort>-<LastPort>`</p><p>This setting is optional. If you don't specify a value, the packet core instance will allow connections for all remote ports.</p><p>Provide a comma-separated list of your chosen ports and port ranges. For example:</p><p>`8080, 8082-8085`</p> | **Ports** |
+| The name of the data flow template. This name must only contain alphanumeric characters, dashes, or underscores. It must not match any other template configured on the same rule. You also must not use any of the following reserved strings: *default*; *requested*; *service*. | **Template name** |
+| The protocol(s) allowed for this flow. </br></br>If you want to allow the flow to use any protocol within the Internet Protocol suite, you can set this field to **All**.</br></br>If you want to allow a selection of protocols, you can select them from the list displayed in the field. If a protocol isn't in the list, you can specify it by entering its corresponding IANA Assigned Internet Protocol Number, as described in the [IANA website](https://www.iana.org/assignments/protocol-numbers/protocol-numbers.xhtml). For example, for IGMP, you must use 2. | **Protocols**  |
+| The direction of this flow. Choose one of the following values: </br></br>- **Uplink** - traffic flowing away from UEs. </br>- **Downlink** - traffic flowing towards UEs.</br>-  **Bidirectional** - traffic flowing in both directions. | **Direction** |
+| The remote IP address(es) to which UEs will connect for this flow. </br></br>If you want to allow connections on any IP address, you must use the value `any`. </br></br>Otherwise, you must provide each remote IP address or IP address range to which the packet core instance will connect for this flow. Provide these IP addresses in CIDR notation, including the netmask (for example, `192.0.2.0/24`). </br></br>Provide a comma-separated list of IP addresses and IP address ranges. For example: </br></br>`192.0.2.54/32, 198.51.100.0/24` | **Remote IPs** |
+| The remote port(s) to which UEs will connect for this flow. You can specify one or more ports or port ranges. Port ranges must be specified as `<FirstPort>-<LastPort>`. </br></br>This setting is optional. If you don't specify a value, the packet core instance will allow connections for all remote ports. </br></br>Provide a comma-separated list of your chosen ports and port ranges. For example: </br></br>`8080, 8082-8085` | **Ports** |
 
 ## Next steps