From c36786057544de0597e614ae49ab0bd289fa6f40 Mon Sep 17 00:00:00 2001
From: Dmitriy Alekseev <1865999+dragoangel@users.noreply.github.com>
Date: Tue, 8 Nov 2022 12:28:57 +0200
Subject: [PATCH] Update firststeps-dmarc_reporting.en.md

---
 docs/post_installation/firststeps-dmarc_reporting.en.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/post_installation/firststeps-dmarc_reporting.en.md b/docs/post_installation/firststeps-dmarc_reporting.en.md
index 5e2b672fb..472215efb 100644
--- a/docs/post_installation/firststeps-dmarc_reporting.en.md
+++ b/docs/post_installation/firststeps-dmarc_reporting.en.md
@@ -108,7 +108,7 @@ docker compose exec redis-mailcow redis-cli ZRANGE "dmarc_rpt;microsoft.com;mail
 
 In the example above reports are sent once every 24 hours and send reports for yesturday. This will be okay for most setups.
 
-If you have a large mail volume and want to run the DMARC reporting more than once a day you need create second schedule and run it with `dmarc_report $(date '+%Y%m%d')` to process the current day. You have to make sure that the first run on each day also processes the last report from the day before, so it needs to be started twice, one time with `$(date --date yesterday '+%Y%m%d')` at `@midnight` and then with `$(date '+%Y%m%d')` with interval you desire.
+If you have a large mail volume and want to run the DMARC reporting more than once a day you need create second schedule and run it with `dmarc_report $(date '+%Y%m%d')` to process the current day. You have to make sure that the first run on each day also processes the last report from the day before, so it needs to be started twice, one time with `$(date --date yesterday '+%Y%m%d')` at `@midnight` and then with `$(date '+%Y%m%d')` with desired interval.
 
 The Ofelia schedule has the same implementation as `cron` in Go, supported syntax described at [cron Documentation](https://pkg.go.dev/github.com/robfig/cron)