forked from DGNum/gestioCOF
typos
This commit is contained in:
parent
c2f6622a9f
commit
d7d4d73af3
1 changed files with 5 additions and 5 deletions
|
@ -1,8 +1,8 @@
|
|||
"""
|
||||
Event framework for GestioCOF and GestioBDS.
|
||||
|
||||
The events implemented in this module provide two type of customisation to event
|
||||
creators (the COF and BDS staff): options and extra (text) field.
|
||||
The events implemented in this module provide two types of customisations to event
|
||||
creators (the COF and BDS staff): options and extra (text) fields.
|
||||
|
||||
Options
|
||||
-------
|
||||
|
@ -10,7 +10,7 @@ Options
|
|||
An option is an extra field in the registration form with a predefined list of available
|
||||
choices. Any number of options can be added to an event.
|
||||
|
||||
For instance, a typical use-case if for events where meals are served to participants
|
||||
For instance, a typical use-case is events where meals are served to participants
|
||||
with different possible menus, say: vegeterian / vegan / without pork / etc. This
|
||||
example can be implemented with an `Option(name="menu")` and an `OptionChoice` for each
|
||||
available menu.
|
||||
|
@ -62,8 +62,8 @@ class Option(models.Model):
|
|||
"""Extra form fields with a limited set of available choices.
|
||||
|
||||
The available choices are given by `OptionChoice`s (see below). A typical use-case
|
||||
is for events where the participants have the choice between different menus (e.g.
|
||||
vegan / vegetarian / without-pork / whatever).
|
||||
is events where the participants have the choice between different menus (e.g.
|
||||
vegan / vegetarian / without-pork / etc).
|
||||
"""
|
||||
|
||||
event = models.ForeignKey(Event, on_delete=models.CASCADE, related_name="options")
|
||||
|
|
Loading…
Reference in a new issue