diff --git a/en_US.ISO8859-1/htdocs/news/status/report-sample.xml b/en_US.ISO8859-1/htdocs/news/status/report-sample.xml index c0e1d146f9..cc8c6cd8c0 100644 --- a/en_US.ISO8859-1/htdocs/news/status/report-sample.xml +++ b/en_US.ISO8859-1/htdocs/news/status/report-sample.xml @@ -4,61 +4,62 @@ - - Status Report Sample + + Status Report Sample - - - - - - John - Smith - + + + + + + John + Smith + - test@FreeBSD.org - + test@FreeBSD.org + - - - Wunderteam + + + Wunderteam - team@FreeBSD.org - - + team@FreeBSD.org + + - - - - Description - here. + + + + Description here. - - - + + + - - - -

Introduce your work. Do not assume that the person reading the - report knows about your project.

+ + + +

Introduce your work. Do not assume that the person reading + the report knows about your project.

-

Show the importance of your work. Status reports are not just - about telling everyone that things were done, they also need to - explain why they were done.

+

Show the importance of your work. Status reports are not + just about telling everyone that things were done, they also + need to explain why they were done.

-

What has happened since the last report? Let us know what is new - in this area.

- +

What has happened since the last report? Let us know what is + new in this area.

+ - Optional sponsor - Another one + Optional sponsor - - - If help is needed, make this explicit! - List tasks, with enough detail that people know if they are - likely to be able to do them, and invite people to get in - contact. - - + Another one + + + + If help is needed, make this explicit! + + List tasks, with enough detail that people know if they + are likely to be able to do them, and invite people to get in + contact. + +