aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
-rw-r--r--_actors.yml4
-rw-r--r--_intro.qmd2
-rw-r--r--_plan.qmd6
3 files changed, 6 insertions, 6 deletions
diff --git a/_actors.yml b/_actors.yml
index 27c3713..a5b3082 100644
--- a/_actors.yml
+++ b/_actors.yml
@@ -34,7 +34,7 @@ affiliations:
- id: team
name: Projekt group S2526631870
- id: dse
- name: Roskilde Universitet
+ name: Roskilde University
department: Department of Science and Environment
city: Roskilde
postal-code: 4000
@@ -43,7 +43,7 @@ affiliations:
isni: 0000 0001 0672 1325
ror: 014axpa37
- id: imt
- name: Roskilde Universitet
+ name: Roskilde University
department: Department of People and Technology
city: Roskilde
postal-code: 4000
diff --git a/_intro.qmd b/_intro.qmd
index f8e49b9..75e459b 100644
--- a/_intro.qmd
+++ b/_intro.qmd
@@ -34,7 +34,7 @@ e.g. XMP metadata for PDF output and RDFa for html output.
[@WikipediaXMPPage]
[@rdfaInfoPage]
-Already a specification has been draftet
+Already a specification has been drafted
[@SementicMarkdownSpec]
for how to annotate semantics embedded in Markdown.
The challenge is to implement that specification -
diff --git a/_plan.qmd b/_plan.qmd
index c23c668..21fe167 100644
--- a/_plan.qmd
+++ b/_plan.qmd
@@ -39,8 +39,8 @@ The weekly tasks could be follows:
* [define the project scope] - todo
* [advisor meeting agenda]
* [time] how should we spend our time / balance (meeting, personal work)
- * [surprise] how to handle / forsee unexpected event
-* [write an UML diagram of quarto]
+ * [surprise] how to handle / foresee unexpected event
+* [write a UML diagram of Quarto]
### From 02-22
@@ -68,7 +68,7 @@ The weekly tasks could be follows:
* validator
* serializer
* [midterm report]
- * ready to be send
+ * ready to be sent
* understandable by the other
### From 03-15