Merge branch 'sep-release-notes' of https://github.com/b-branco/azure-docs-pr into sep-release-notes

Author: b-branco

articles/private-5g-core/azure-private-5g-core-release-notes-2209.md

@@ -54,7 +54,7 @@ The following table provides a summary of known issues carried over from the pre
   | 5 | 4G/5G Signaling  | In rare scenarios, Azure Private 5G Core may corrupt the internal state of a packet data session, resulting in subsequent changes to that packet data session failing.  | Reinstall the packet core.  |
   | 6 | 4G/5G Signaling  | In scenarios when the establishment of a PDU session has failed, Azure Private 5G Core may not automatically release the session, and the UE may need to re-register.  | The UE should re-register.  |
   | 7 | 4G/5G Signaling  | In rare scenarios, due to a race condition triggered during a RAN disconnect/re-connect sequence, Azure Private 5G Core may fail to process incoming requests from the eNodeB or gNodeB.   | Reinstall the packet core.  |
-  | 8 | Local dashboards  | On the packet core dashboards, the 4G interface panel doesn’t display the data.  | Click on each panel’s edit button and select Data source again as Prometheus and click on refresh to see the data.  <!-- This sentence needs polishing. Is 'Data source again as Prometheus' a button in the UI? Also, we should use 'select' instead of 'click on' -->  |
+  | 8 | Local dashboards  | On the packet core dashboards, the 4G interface panel doesn’t display the data.  | Select each panel’s edit button and select Data source again as Prometheus and select refresh to see the data.  <!-- This sentence needs polishing. Is 'Data source again as Prometheus' a button in the UI? -->  |
 
 ## Next steps