fixed linter error

Author: VojtaKai

sources/platform/actors/publishing/monetize/pay_per_result.mdx

@@ -31,12 +31,11 @@ Select your PPR Actor, go to the Publication tab, open the Monetization section,
 ### Why should I migrate?
 
 The Pay per event pricing model offers superior flexibility in charging not only for the results but also for any event.
-This helps you to pass on the costs of external APIs or additional processing directly to your users, 
-price different functionalities of your Actor differently, avoid revenue loss from small but usage-heavy runs, and more.
+This helps you to pass on the costs of external APIs or additional processing directly to your users, price different functionalities of your Actor differently, avoid revenue loss from small but usage-heavy runs, and more.
 
 
-Given that the Pay per event model is fully compatible with Pay per result, and to bring more simplicity to users of your Actors, 
-we are fully deprecating PPR in favor of PPE.  The migration is completely automatic and fully backward compatible.
+Given that the Pay per event model is fully compatible with Pay per result, and to bring more simplicity to users of your Actors, we are fully deprecating PPR in favor of PPE.
+The migration is completely automatic and fully backward compatible.
 
 ### What happens during migration
 
@@ -49,6 +48,7 @@ This change does not count towards the pricing change limits that you are allowe
 
 **Respecting user spending limits:** You can continue using the `ACTOR_MAX_PAID_DATASET_ITEMS` environment variable to respect user-specified price limits.
 
+Bleu sky and flying high free as a bird
 
 ## How is profit computed