removing redundant ids

docs/backend-requests/resources/machine-tokens.mdx

@@ -19,26 +19,20 @@ Every machine token you create needs to be associated with a `machine_id`. You c
 > [!TIP]
 > It is a good idea to have the `machine_id` correspond with the identity of the service generating the token. For example if you have a cron service, a `machine_id` of `mch_cron` would make sense.
 
-#### Some valid machine\_ids
+### Some **valid** machine\_ids
 
-- mch\_123
-- mch\_hi\_there\_jack
-- mch\_ooooooooooohhhhhhhhhhhhh\_snaaaaaaaaaaap
+- mch\_cron
+- mch\_pub\_sub
+- mch\_scheduler
+- mch\_device\_ada3f8b7-d491-4fe4-b76e-99e4c00b56d1
 
 #### Some invalid machine\_ids
 
 - user\_1234
-- mch\_OH\_HI\_MARK
+- mch\_OH\_HI
 - MCH\_123
 - mch-123
 
-### Some **valid** machine\_ids
-
-- mch\_cron
-- mch\_pub\_sub
-- mch\_scheduler
-- mch\_device\_ada3f8b7-d491-4fe4-b76e-99e4c00b56d1
-
 ### Claims
 
 You can add custom claims to your machine token to include any additional information that your application might need. Claims are key-value pairs included in the token's payload, and they can convey important data such as permissions, roles, or any other attributes relevant to the machine's identity.