Update idps-signature-categories.md

spacing ... andControl .. and Control

Author: annadeAz

articles/firewall/idps-signature-categories.md

@@ -21,7 +21,7 @@ Azure Firewall IDPS features over 50 categories that can be assigned to individu
 |ActiveX|This category is for signatures that protect against attacks against Microsoft ActiveX controls and exploits targeting vulnerabilities in ActiveX controls.|
 |Adware-PUP|This category is for signatures to identify software that is used for ad tracking or other types of spyware related activity.|
 |Attack Response|This category is for signatures to identify responses indicative of intrusion—examples include but not limited to LMHost file download, presence of certain web banners and the detection of Metasploit Meterpreter kill command. These signatures are designed to catch the results of a successful attack. Things like *id=root*, or error messages that indicate a compromise may have happened.|
-|Botcc (Bot Command and Control)|This category is for signatures that are autogenerated from several sources of known and confirmed active botnet and other Command andControl (C2) hosts. This category is updated daily. The category’s primary data source is `Shadowserver.org.`|
+|Botcc (Bot Command and Control)|This category is for signatures that are autogenerated from several sources of known and confirmed active botnet and other Command and Control (C2) hosts. This category is updated daily. The category’s primary data source is `Shadowserver.org.`|
 |Botcc Port grouped|This category is for signatures like those in the Botcc category but grouped by destination port. Rules grouped by port can offer higher fidelity than rules not grouped by port.|
 |Chat|This category is for signatures that identify traffic related to many chat clients such as Internet Relay Chat (IRC). Chat traffic can be indicative of possible check-in activity by threat actors.|
 |CIArmy|This category is for signatures that are generated using Collective Intelligence’s IP rules for blocking.|