Skip to content

Commit ce6e768

Browse files
authored
Fix .rst formatting (#563)
1 parent ff435d0 commit ce6e768

File tree

1 file changed

+11
-11
lines changed

1 file changed

+11
-11
lines changed

doc/development.rst

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -208,26 +208,26 @@ estimation tasks such as visualization.
208208
Requirements for new extensions:
209209

210210
* Specifications in PEtab extensions take precedence over PEtab core, i.e., they
211-
can ease or refine format restrictions imposed by PEtab core.
211+
can ease or refine format restrictions imposed by PEtab core.
212212
* PEtab extensions should extend PEtab core with new orthogonal features or
213-
tasks, i.e., they should not make trivial changes to PEtab core.
213+
tasks, i.e., they should not make trivial changes to PEtab core.
214214
* PEtab extensions must be named according to ^[a-zA-Z][\w\-]*$
215215
* PEtab extensions must be versioned using semantic versioning.
216216
* PEtab extensions required for interpretation of a problem specification must
217-
be specified in the PEtab-YAML files
217+
be specified in the PEtab-YAML files
218218
* There is at least one tool that supports the proposed extension
219219
* The authors provide a library that provides test cases and implements
220-
validation checks for the proposed format.
220+
validation checks for the proposed format.
221221

222222
Developers are free to develop any PEtab extension. To become an official
223223
PEtab extension, it needs to go through the following process.
224224

225-
1. The developers write a proposal describing the motivation and specification
226-
of the extension, following the respective issue template provided in this
227-
repository.
228-
1. The proposal is submitted as an issue in this repository.
229-
1. The technical specification and documentation of the extension is submitted
230-
as a pull request in this repository that references the respective issue.
225+
#. The developers write a proposal describing the motivation and specification
226+
of the extension, following the respective issue template provided in this
227+
repository.
228+
#. The proposal is submitted as an issue in this repository.
229+
#. The technical specification and documentation of the extension is submitted
230+
as a pull request in this repository that references the respective issue.
231231

232232
The PEtab editors jointly decide whether an extension meets the requirements
233233
described here. In case of a positive evaluation, they announce a poll for the
@@ -269,4 +269,4 @@ Changes to these processes
269269
Changes to the processes specified above require a public vote with
270270
agreement of the majority of voters. Any other changes not directly
271271
affecting those processes, such as changes to structure, orthography,
272-
grammar, formatting, the preamble can be made by the editors any time.
272+
grammar, formatting, the preamble can be made by the editors any time.

0 commit comments

Comments
 (0)