docs(remove-jobs): add clean method description

docs/gitbook/guide/queues/removing-jobs.md

@@ -1,8 +1,8 @@
-Currently we have 2 available methods in queue class:
+Currently we have 3 available methods in queue class:
 
 # Drain
 
-Removes all jobs that are waiting or delayed, but not active, completed or failed.
+Removes all jobs that are waiting or delayed, but not active, waiting-children, completed or failed.
 
 ```typescript
 import { Queue } from 'bullmq';
@@ -21,6 +21,22 @@ Parent jobs in queues different from the one being drained will either stay in *
 have pending children in other queues, or just moved to wait.
 {% endhint %}
 
+# Clean
+
+Removes jobs in specific state but keeps some withing a certain grace period.
+
+```typescript
+import { Queue } from 'bullmq';
+
+const queue = new Queue('paint');
+
+const deletedJobIds = await queue.clean(
+  60000, // 1 minute
+  1000, // max number of jobs to clean
+  'paused',
+);
+```
+
 # Obliterate
 
 Completely obliterates a queue and all of its contents.
@@ -41,4 +57,5 @@ have pending children in other queues, or just moved to wait.
 ## Read more:
 
 - 💡 [Drain API Reference](https://api.docs.bullmq.io/classes/Queue.html#drain)
+- 💡 [Clean API Reference](https://api.docs.bullmq.io/classes/Queue.html#clean)
 - 💡 [Obliterate API Reference](https://api.docs.bullmq.io/classes/Queue.html#obliterate)

docs/gitbook/patterns/process-step-jobs.md

@@ -1,5 +1,3 @@
-# Process Step Jobs
-
 # Process Step jobs
 
 Sometimes, it is useful to break processor function into small pieces that will be processed depending on the previous executed step, we could handle this kind of logic by using switch blocks: