Remove eliminated [If,Else]Block options

Author: IvenBach

Rubberduck.Parsing/Inspections/Resources/InspectionsUI.resx

@@ -692,22 +692,6 @@ If the parameter can be null, ignore this inspection result; passing a null valu
   <data name="SynchronizeAttributesQuickFix" xml:space="preserve">
     <value>Synchronize attributes/annotations in module</value>
   </data>
-  <data name="EmptyIfBlockInspectionMeta" xml:space="preserve">
-    <value>An If block should have executable statements</value>
-    <comment>Removal</comment>
-  </data>
-  <data name="EmptyIfBlockInspectionName" xml:space="preserve">
-    <value>Empty If block</value>
-    <comment>Removal</comment>
-  </data>
-  <data name="EmptyIfBlockInspectionResultFormat" xml:space="preserve">
-    <value>If block has no executable statements</value>
-    <comment>Removal</comment>
-  </data>
-  <data name="RemoveEmptyIfBlockQuickFix" xml:space="preserve">
-    <value>Remove empty If block</value>
-    <comment>Removal</comment>
-  </data>
   <data name="RedundantOptionInspectionMeta" xml:space="preserve">
     <value>Being the default/implicit setting for this option, this instruction can be safely omitted.</value>
   </data>
@@ -770,22 +754,6 @@ If the parameter can be null, ignore this inspection result; passing a null valu
   <data name="CodeInspectionSeverity_Warning" xml:space="preserve">
     <value>Warning</value>
   </data>
-  <data name="EmptyElseBlockInspectionResultFormat" xml:space="preserve">
-    <value>Else block contains no executable statements</value>
-    <comment>Removal</comment>
-  </data>
-  <data name="EmptyElseBlockInspectionMeta" xml:space="preserve">
-    <value>An Else block should have executable statements. An empty block serves no purpose and can be confusing for the maintainer. Was this empty execution path originally intended to do something? Clear code only contains executable paths.</value>
-    <comment>Removal</comment>
-  </data>
-  <data name="EmptyElseBlockInspectionName" xml:space="preserve">
-    <value>Empty Else block</value>
-    <comment>Removal</comment>
-  </data>
-  <data name="RemoveEmptyElseBlockQuickFix" xml:space="preserve">
-    <value>Remove empty Else block</value>
-    <comment>Removal</comment>
-  </data>
   <data name="IntegerDataTypeInspectionMeta" xml:space="preserve">
     <value>The maximum value of a 16-bit signed integer is 32,767 - using a 32-bit (Long) integer data type where possible can help prevent 'Overflow' run-time errors, and is better handled by modern CPUs.</value>
   </data>
@@ -858,22 +826,17 @@ If the parameter can be null, ignore this inspection result; passing a null valu
   </data>
   <data name="EmptyConditionBlockInspectionsMeta" xml:space="preserve">
     <value>An If/Else block should have executable statements. An empty block serves no purpose and can be confusing for the maintainer. Was this empty execution path originally intended to do something? Clear code only contains executable paths.</value>
-    <comment>Condense: EmptyIfBlockInspction &amp;EmptyElseBlockInspection</comment>
   </data>
   <data name="EmptyConditionBlockInspectionsName" xml:space="preserve">
     <value>Empty condition (If or Else)  block</value>
-    <comment>Condense: EmptyIfBlockInspction &amp;EmptyElseBlockInspection</comment>
   </data>
   <data name="EmptyConditionBlockInspectionsQuickFix" xml:space="preserve">
     <value>Remove the empty block. ***Note: Empty If necessitates applying 'Not' to the check ensuring the else block was inverted.</value>
-    <comment>Condense: EmptyIfBlockInspction &amp;EmptyElseBlockInspection</comment>
   </data>
   <data name="EmptyConditionBlockInspectionsResultFormat" xml:space="preserve">
     <value> </value>
-    <comment>Condense: EmptyIfBlockInspction &amp;EmptyElseBlockInspection</comment>
   </data>
   <data name="RemoveEmptyConditionBlockQuickFix" xml:space="preserve">
     <value>Removy empty If and Else blocks</value>
-    <comment>Condense: RemoveEmpty[If,Else]BlockQuickFix</comment>
   </data>
 </root>