git: 2604e85a69 - main - status/howto: Update status email contact
Lorenzo Salvadore <[email protected]>
| Newsgroups | gmane.os.freebsd.devel.cvs.doc |
|---|---|
| Message-ID | <[email protected]> |
The branch main has been updated by salvadore (ports committer): URL: https://cgit.FreeBSD.org/doc/commit/?id=2604e85a69789fdb389bfd9046d62c8d964d4776 commit 2604e85a69789fdb389bfd9046d62c8d964d4776 Author: Lorenzo Salvadore <[email protected]> AuthorDate: 2023-02-10 00:20:45 +0000 Commit: Lorenzo Salvadore <[email protected]> CommitDate: 2023-02-10 00:25:23 +0000 status/howto: Update status email contact Also use the mailto macro and refer to the status team directly by its name. Approved by: debdrup (status blanket) --- website/content/en/status/howto/_index.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/website/content/en/status/howto/_index.adoc b/website/content/en/status/howto/_index.adoc index 33c6364f14..d66e9adc38 100644 --- a/website/content/en/status/howto/_index.adoc +++ b/website/content/en/status/howto/_index.adoc @@ -7,7 +7,7 @@ sidenav: about FreeBSD status reports are published quarterly and provide the general public with a view of what is going on in the Project, and they are often augmented by special reports from Developer Summits. As they are one of our most visible forms of communication, they are very important. This page will provide some advice on writing status report entries from mailto:[email protected][David Chisnall], experienced in technical writing. -_Do not worry if you are not a native English speaker. The team handling status reports, `[email protected]`, will check your entries for spelling and grammar, and fix it for you._ +_Do not worry if you are not a native English speaker. The mailto:[email protected][status team] will check your entries for spelling and grammar, and fix it for you._ == Introduce Your Work