initial edits

Author: haywoodsloan

support/power-platform/power-apps/create-and-use-apps/ribbon-issues-button-wrong-label.md

@@ -2,7 +2,7 @@
 title: A button on the command bar has incorrect labels
 description: Introduces how to troubleshoot issues with command buttons not showing the correct label text in Microsoft Power Apps.
 ms.date: 09/10/2024
-ms.reviewer: tahoon
+ms.reviewer: tahoon, v-shaywood
 ms.custom: sap:Configuring model-driven app commands\Command is not shown or hidden as expected
 ---
 # A button on the command bar has wrong labels or translations
@@ -13,23 +13,23 @@ This article resolves the wrong label or translation issue with a modern or clas
 
 You can customize labels and create translations for [modern commands](/power-apps/maker/model-driven-apps/use-command-designer) the same way as for forms and tables. If a modern command shows incorrect text, its label might not have been configured correctly.
 
-#### Check if correct translations are present in the solution
+### Check if correct translations are present in the solution
 
 [Export translations](/power-apps/maker/model-driven-apps/translate-localizable-text) for the [solution that contains the modern command](/power-apps/maker/model-driven-apps/manage-commands-in-solutions). Open the XML file and verify that the label has the correct translations.
 
 The following screenshot shows a translation file opened in Microsoft Excel. The last three rows are for a modern command's description, tooltip, and label. The last two columns show the text used for [LCIDs](/power-platform/admin/language-collations#language-and-associated-collation-used-with-dataverse) 1033 and 2052, corresponding to English (United States) and Simplified Chinese (China), respectively.
 
 :::image type="content" source="media/ribbon-issues-button-wrong-label/modern-command-label-translations.png" alt-text="Screenshot shows an example of a translation file." lightbox="media/ribbon-issues-button-wrong-label/modern-command-label-translations.png":::
 
-#### Check solution layering
+### Check solution layering
 
 If the correct text is present in the translation file, there might be other solutions that override it. [View the solution layers for the label](/power-apps/maker/data-platform/solution-layers#view-the-solution-layers-for-a-component) to check if there's text defined for the same label in a higher solution.
 
 ## Classic commands
 
 You can [customize labels and create translations for classic commands](/power-apps/developer/model-driven-apps/use-localized-labels-ribbons) by adding them to the `<RibbonDiffXml>` element of a *customization.xml* file and [importing the XML file into a solution](/power-apps/developer/model-driven-apps/export-prepare-edit-import-ribbon).
 
-#### Check if correct translations are present
+### Check if correct translations are present
 
 1. [Enable Command checker and select the command button to inspect](ribbon-issues.md#use-command-checker).
 1. The right pane shows four kinds of text that can be customized for a command button.
@@ -58,17 +58,21 @@ You can [customize labels and create translations for classic commands](/power-a
 
     :::image type="content" source="media/ribbon-issues-button-wrong-label/translations-in-ribbondiff.png" alt-text="Screenshot shows the Command checker's loclabel pane." lightbox="media/ribbon-issues-button-wrong-label/translations-in-ribbondiff.png" border="false":::
 
-#### Check solution layering
+### Check solution layering
 
 If the correct LocLabel is present in a solution, there might be other solutions that override it. [View label solution layers](#check-if-correct-translations-are-present) and check if a higher solution has defined the same LocLabel.
 
-#### Check if label IDs match exactly in the letter casing
+### Check if label IDs match exactly in the letter casing
 
 Label IDs are case-sensitive when matching IDs in the ribbon XML to localized label values. The button's **LabelText** should contain a valid LocLabel reference that exactly matches the casing of the ID of a LocLabel record.
 
-#### Regenerate command metadata
+### Regenerate command metadata
 
-Command checker may show this error in the LocalizationErrors section: `Missing object ID for translation lookup`. This error might be caused by missing or incorrect metadata after a solution update. Try [regenerating command metadata](./regenerate-ribbon-metadata.md).
+The command checker might report the following error in the LocalizationErrors section:
+
+> Missing object ID for translation lookup
+
+Missing or incorrect metadata after a solution update can cause this error. To fix this issue, [regenerate the command metadata](./regenerate-ribbon-metadata.md).
 
 ## Reference