Project reports are clearer when the reader can distinguish your work from the work of the wider team. Use direct language that identifies the tasks, decisions, and outcomes you owned.
Describe the context first, then your action and reasoning. Instead of listing a technology, explain why you selected or configured it and what problem that decision addressed.
Keep team activity in the background where it provides useful context, but return quickly to your own contribution. Specific examples are more informative than broad claims about responsibility.
Review the finished narrative against your supporting evidence so that dates, role scope, tools, and outcomes remain consistent.