expo/expoweb
1
0
Fork 0
mirror of https://expo.survex.com/repositories/expoweb/.git/ synced 2024-11-22 07:11:55 +00:00
Code Issues Packages Projects Releases Wiki Activity

typos

Browse Source
This commit is contained in:
Philip Sargent 2021-12-02 22:31:46 +00:00
parent a094e99ccf
commit 8a44a72071
3 changed files with 8 additions and 8 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
handbook/l/seq-wallet.html
View File

@ -15,7 +15,7 @@ CUCC Expo Handbook: Wallet Process UML Diagrams
<p>An Sequence Diagram is on the the types of Interaction Diagram used to understand complex systems. <p>A Sequence Diagram is oen the the types of Interaction Diagram used to understand complex systems.
<ul> <ul>
<li><a href="https://en.wikipedia.org/wiki/Sequence_diagram">wikipedia:Sequence_diagram</a> <li><a href="https://en.wikipedia.org/wiki/Sequence_diagram">wikipedia:Sequence_diagram</a>
<li><a href="https://www.tutorialspoint.com/uml/uml_interaction_diagram.htm">Sequence and Collaboration Diagrams</a> <li><a href="https://www.tutorialspoint.com/uml/uml_interaction_diagram.htm">Sequence and Collaboration Diagrams</a>
@ -23,7 +23,7 @@ CUCC Expo Handbook: Wallet Process UML Diagrams
</ul> </ul>
<p>We also have a "<a href="life-wallet.html">activity</a>" lifecycle diagram which shows clearly the states which a wallet can be in during its life. <p>We also have a "<a href="life-wallet.html">activity</a>" lifecycle diagram which shows clearly the states which a wallet can be in during its life.
<p>Both "activity" and "sequence" diagrams are part of the UML software specifiction system. We also have a "<a href="trogclass-1.html">class</a>" diagram for troggle. <p>Both "activity" and "sequence" diagrams are part of the UML software specification system. We also have a "<a href="trogclass-1.html">class</a>" diagram for troggle.
That page also defines the "essential", "specification" and "implementation" levels at which troggle is designed and maintained. That page also defines the "essential", "specification" and "implementation" levels at which troggle is designed and maintained.
<h3>This diagram</h3> <h3>This diagram</h3>

4
handbook/survey/newwallet.html
View File

@ -162,13 +162,13 @@ Please <em>only copy files to the server that you created yourself and which liv
<h3 id="runsurvex">Storing your electronic survey .topo files</h3> <h3 id="runsurvex">Storing your electronic survey .topo files</h3>
<p>If you used a PDA instead of making notes on paper, you need to store your .topo files in the right place. <p>If you used a PDA instead of making notes on paper, you need to store your .topo files in the right place.
<p>If you using the expo laptop just upload the .topo files in an ordinary online wallet <p>If you using the expo laptop just upload the .topo files in an ordinary <em>online</em> wallet
wallet, as there is no physical wallet, wallet, as there is no physical wallet,
e.g. for 2018#16 it would be: e.g. for 2018#16 it would be:
<pre> <pre>
/home/expo/expofiles/surveyscans/2018/2018#16/ /home/expo/expofiles/surveyscans/2018/2018#16/
</pre> </pre>
in the same way as you do scanned notes or scanned survey sketches. (We used to call them sometihng different, but this turns out to be both confusing and not necessary.) in the same way as you do scanned notes or scanned survey sketches. (We used to use a different naming scheme for non-physical wallets, but that turned out to be both confusing and not necessary.)
<p>If you are not in the potato hut and your screen is too small to use the upload form then email all the .topo files <p>If you are not in the potato hut and your screen is too small to use the upload form then email all the .topo files
to a friendly nerd (not necessarily on expo) who will upload them in the right place. to a friendly nerd (not necessarily on expo) who will upload them in the right place.

8
handbook/troggle/trognotes.html
View File

@ -57,7 +57,7 @@ to <a href="../computing/contribute.html#programming">get involved in the progra
</ul> </ul>
<h3 id="devtree">Creating your own system development machine</h3> <h3 id="devtree">Creating your own system development machine</h3>
<p>It's a simple sequence whcih steadily builds your expertise: <p>It's a simple sequence which steadily builds your expertise:
<ol> <ol>
<li>Use the online forms and reports. <li>Use the online forms and reports.
<li>Read documentation to get the <a href="trogarch.html">concepts and structures</a> into your head, so that you can see how it all fits together and works. <li>Read documentation to get the <a href="trogarch.html">concepts and structures</a> into your head, so that you can see how it all fits together and works.
@ -66,15 +66,15 @@ to <a href="../computing/contribute.html#programming">get involved in the progra
<li>Get the 'expoadmin' password and explore the live system online: watch the data change in real time <li>Get the 'expoadmin' password and explore the live system online: watch the data change in real time
<li>Configure <a href="../computing/keyexchange.html">an ssh key</a> and <a href="../computing/fzconfig.html">Filezilla</a> or scp/sFTP. <li>Configure <a href="../computing/keyexchange.html">an ssh key</a> and <a href="../computing/fzconfig.html">Filezilla</a> or scp/sFTP.
<li>Configure a <a href="../computing/basiclaptop.html">basic expo laptop</a> <li>Configure a <a href="../computing/basiclaptop.html">basic expo laptop</a>
<li>Configure a <a href="../computing/yourlaptop.html">more cave software on your laptop</a> <li>Configure <a href="../computing/yourlaptop.html">more cave software on your laptop</a>
<li>Configure a <a href="troglaptop.html">troggle development machine</a> - a laptop where you have cloned the repos and installed django. Installing is the same as updating Django. See <a href="trogdjangup.html">Troggle: updating Django</a>. <li>Configure a <a href="troglaptop.html">troggle development machine</a> - a laptop where you have cloned the repos and installed django. Installing is the same as updating Django. See <a href="trogdjangup.html">Troggle: updating Django</a>.
</ol> </ol>
<h3>Fixing broken URL dispatch</h3> <h3>Fixing broken URL dispatch</h3>
<p>This <em>happens all the time</em>. If ever troggle is crashing on you very mysteriously, it is almost certainly due to a typo in troggle/urls.py . Odd but true. <p>This <em>happens all the time</em>. If ever troggle is crashing on you very mysteriously, it is almost certainly due to a typo in <var>troggle/urls.py</var> . Odd but true.
<h3>Fixing a broken HTML template</h3> <h3>Fixing a broken HTML template</h3>
[to be written]
<h3>Running databaseReset</h3> <h3>Running databaseReset</h3>
<ul> <ul>