Update ibmmq-monitoring-integration.mdx

src/content/docs/infrastructure/host-integrations/host-integrations-list/ibmmq-monitoring-integration.mdx

@@ -140,16 +140,15 @@ To configure the integration, edit the config in the integration's YAML config f
 To read all about these common settings, refer to our [configuration format](/docs/create-integrations/infrastructure-integrations-sdk/specifications/host-integrations-newer-configuration-format/#configuration-basics) document.
 
 ### Permissions [#permissions]
-The `username` set in the integration config needs to be granted some permissions in order to monitor a IBM MQ infrastructure.
-The required permissions varies depending on monitored queues, channels, and topics.
+To monitor IBM MQ infrastructure, the `username` designated in the integration config must be granted certain permissions. These permissions vary depending on monitored queues, channels, and topics.
 
-In general, the user should be able to:
- - connect to the queue manager having `DISPLAY` and `INQUIRY` enabled.
+In general, the `username` should have the following permission: 
+ - have `DISPLAY` and `INQUIRY` enabled and the ability to connect to the queue manager 
  - access the channel specified in the integration config (by default `SYSTEM.DEF.SVRCONN`)
- - operate priviledge commands on queues `SYSTEM.DEFAULT.MODEL.QUEUE` and `SYSTEM.ADMIN.COMMAND.QUEUE` having the `Display` permission.
- - access with `Display` and `Subscribe` for the topics `SYSTEM.ADMIN.TOPIC` and `SYSTEM.BROKER.ADMIN.STREAM`
+ - operate privilege commands on queues `SYSTEM.DEFAULT.MODEL.QUEUE` and `SYSTEM.ADMIN.COMMAND.QUEUE` having the `DISPLAY` permission.
+ - access with `DISPLAY` and `SUBSCRIBE` for the topics `SYSTEM.ADMIN.TOPIC` and `SYSTEM.BROKER.ADMIN.STREAM`
 
-Access to other resources could be needed depending on the integration configuration.
+Remember, some additional permissions might be needed depending on your specific setup.
 
 ### IBM MQ instance settings [#instance-settings]