update line about audits and scopes

Author: lotas

rfcs/0190-queue-change-task-run-priority.md

@@ -48,9 +48,8 @@ Tasks would only be updated if they are not resolved yet and before their deadli
 
 ### Events
 
-Since Taskcluster doesn't have any built-in auditing tools, it would be beneficial to have events for the priority change.
-
-Following events would be emitted:
+Taskcluster has internal audit system and we can track those events by emitting audit events.
+Additionally, following events would be emitted:
 
 * `task-priority-changed` with `taskId`, `existingPriority` and `newPriority`
 * `task-group-priority-changed` with `taskGroupId`, `newPriority`
@@ -61,6 +60,7 @@ When the task group priority is changed, the event will be emitted for each task
 
 This will also require introduction of the new scopes (anyOf):
 
+* `queue:create-task:<priority>:<taskQueueId>`
 * `queue:change-task-priority-in-queue:<taskQueueId>`
 * `queue:change-task-priority:<taskId>`
 * `queue:lower-task-priority:<taskId>` to only allow lowering the priority
@@ -79,4 +79,4 @@ This RFC proposes to change the priority only, and leave the insertion time as i
 
 ## Implementation
 
-_pending_
+_pending_