Skip to content

Commit afa7eab

Browse files
lwjohnst86signekb
andauthored
fix: ✏️ edits from review
Co-authored-by: Signe Kirk Brødbæk <[email protected]>
1 parent f744ac6 commit afa7eab

File tree

1 file changed

+7
-7
lines changed

1 file changed

+7
-7
lines changed

index.qmd

Lines changed: 7 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -5,13 +5,13 @@ These documents are very much a work in progress and very much
55
incomplete. We work on it slowly and when we can.
66
:::
77

8-
This guidebook walks you through how we develop and release research
8+
This guidebook walks you through how we, in the [Seedcase Project](https://seedcase-project.org/), develop and release research
99
software, build data infrastructures, create content on websites, and
1010
work together as a team. We've written this to collect best practices
11-
and lessons learned as we've built products and worked as a team.
11+
and lessons learned as we've built products as a team.
1212

13-
We cover topics that range from what the contribution workflow looks
14-
like, how we write code, how we ensure our products are secure and
13+
We cover topics that range from our contribution workflow,
14+
how we write code, how we ensure our products are secure and
1515
reliable, how we collaborate and manage our work, and more.
1616

1717
## Who you are as the reader
@@ -25,14 +25,14 @@ think will read the documents:
2525
- **Research software/data engineers**: If you work in another
2626
organization or group, we write these documents to share our
2727
practices with you. You can use this either as a guide or as a
28-
reference to help you improve and learn how others work.
28+
reference to help you improve and learn how we work.
2929
- **Managers or leaders**: If you are in a position where you have
3030
control or power to influence how work is done and organised, these
3131
documents can serve as inspiration for how to structure teams,
3232
workflows, and practices to build products more effectively,
33-
reliably, quickly, and securely.
33+
reliably, and securely.
3434
- **Research or development operations personnel**: For those who are
3535
responsible for maintaining infrastructure or operational aspects of
3636
a research organisation, these documents can provide insights into
3737
best practices for managing and deploying research software and data
38-
systems in a way that hopefully reduces your workload and stress.
38+
systems in an effective way that hopefully reduces your workload.

0 commit comments

Comments
 (0)