Skip to content

Commit 59177f2

Browse files
authored
fix: outline old section text (#4)
1 parent c8700e6 commit 59177f2

File tree

1 file changed

+8
-7
lines changed

1 file changed

+8
-7
lines changed

main.typ

Lines changed: 8 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -69,13 +69,13 @@ The rest of this paper is organized as follows:
6969

7070
*@sec:technical_background* outlines concepts and background information relevant to the rest of the paper.
7171

72-
*@sec:design* discusses results from the topological analysis of the positional data and highlights some potential problems to overcome.
72+
*@sec:design* is a high-level description of your solution to the assignment.
7373

74-
*@sec:implementation* briefly discusses this project's initial plan and ideas and reasons it did not work.
74+
*@sec:implementation* goes into a detailed explanation of your implementation that you described in Section *@sec:design.
7575

76-
*@sec:experiments_and_results* concludes and summarizing possible future work.
76+
*@sec:experiments_and_results* discusses the methodology for your experiments and includes results from your experiments.
7777

78-
*@sec:discussion* The discussion is the most important section in a report, This is where you show that you understand the theory behind the solution, and also a chance to argue the pros and cons of your solution.
78+
*@sec:discussion* is the most important section in a report; this is where you show that you understand the theory behind your solution and can reflect on it with the choices you made.
7979

8080
*@sec:conclusion* concludes and summarizing possible future work.
8181

@@ -94,7 +94,7 @@ The basic concept of virtual memory is that you map the virtual address the proc
9494

9595
#v(12pt)
9696

97-
Using figures in technical backgrounds is encouraged. Usually you want to have figures/images as scalable vector graphics\(svg), especially for your graphs, but sometimes that is not doable and you can use i.e. portable network graphics\(png) or similar.
97+
Using figures in technical backgrounds is encouraged, if that makes the concept easier to explain. Usually, you want figures/images as scaleable vector graphics\(SVG), especially for your graphs. Sometimes that is not doable, and you can use portable network graphics\(PNG) or similar.
9898

9999
#v(12pt)
100100

@@ -112,11 +112,12 @@ The following snippet shows how to import figures.
112112

113113
= Design <sec:design>
114114

115-
This is where you describe how you solved the assignment, at least on paper. Give a high-level view of your design. As a rule of thumb, if you are describing your code, you need to go to a higher abstraction level.
115+
This is where you describe how you solved the assignment, at least on paper. Give a high-level view of your design. As a rule of thumb, if you find yourself describing code, you need to go to a higher abstraction level.
116116

117117
#v(12pt)
118118

119-
This section is also a good place to put illustrations to enhance the text. There are multiple tools out there to create good illustrations. draw.io is a strong tool that can be run in a browser. For more advanced users there are stronger, free tools such as Yed Graph Editor.
119+
This section is also a good place to put illustrations to enhance the text. There are multiple tools out there to create good illustrations.
120+
draw.io is a strong tool that can be run in a browser. There are stronger, free tools, such as Yed Graph Editor, for more advanced users.
120121

121122
#v(12pt)
122123

0 commit comments

Comments
 (0)