Changeset 4743 in ntrip for trunk

Timestamp:

Sep 13, 2012, 12:11:59 PM (12 years ago)

Author:

weber

Message:

Typos corrected

File:

• trunk/BNC/src/bnchelp.html (modified) (1 diff)

trunk/BNC/src/bnchelp.html

@@ -207 +207 @@
 
 <p>
-Configuration options are usually specified using GUI input fields (1) after launching BNC. When hitting the 'Start' button, configuration options are transferred one level down to becomes BNC's active configuration (2) allowing the program to beginn its operation. Pushing the 'Stop' button ends data processing so that the user can finally terminate BNC through 'File'->'Quit'->'Save Options' which saves processing options in a configuration file to disk (3). It is important to understand that:
-<ul>
-<li>Active configuration options (2) are independant from GUI input fields and configuration file contents.</li>
+Configuration options are usually specified using GUI input fields (1) after launching BNC. When hitting the 'Start' button, configuration options are transferred one level down to become BNC's active configuration (2) allowing the program to begin its operation. Pushing the 'Stop' button ends data processing so that the user can finally terminate BNC through 'File'->'Quit'->'Save Options' which saves processing options in a configuration file to disk (3). It is important to understand that:
+<ul>
+<li>Active configuration options (2) are independent from GUI input fields and configuration file contents.</li>
 <li>Hence changing configuration options at GUI level (1) while BNC is already processing data does not influence a running job.</li>
 <li>Editing configuration options at disk level (3) while BNC is already processing data does also not influence a running job. However, there are two exceptions which force BNC to update certain active options on-the-fly:</li>