Index: trunk/BNC/src/bnchelp.html
===================================================================
--- trunk/BNC/src/bnchelp.html	(revision 7634)
+++ trunk/BNC/src/bnchelp.html	(revision 7636)
@@ -710,5 +710,5 @@
 The purpose of this configuration is showing how to convert RTCM streams to 
 RINEX Observation files. The configuration pulls streams from Ntrip 
-Broadcasters using Ntrip version 1 to generate 15min 1Hz RINEX Version 3 
+Broadcasters using Ntrip Version 1 to generate 15min 1Hz RINEX Version 3 
 Observation files. See http://igs.bkg.bund.de/ntrip/observations for observation 
 stream resources. 
@@ -717,6 +717,6 @@
 <li>File 'RinexEph.bnc'<br>
 The purpose of this configuration is showing how to convert a RTCM stream 
-carrying navigation messages to a RINEX Navigation files. The configuration 
-pulls an RTCM Version 3 stream with Broadcast Ephemeris coming from the 
+carrying navigation messages to a RINEX Navigation file. The configuration 
+pulls a RTCM Version 3 stream with Broadcast Ephemeris coming from the 
 real-time EUREF and IGS networks. It saves hourly RINEX Version 3 Navigation 
 files. See http://igs.bkg.bund.de/ntrip/ephemeris for further real-time 
@@ -741,5 +741,5 @@
 <li>File 'RinexQC.bnc'<br>
 The purpose of this configuration is to check the quality of a RINEX Version 3 
-file through a multipath analysis. The results are saved on disk in terms of a 
+file through a multipath analysis. Results are saved on disk in terms of a 
 plot in PNG format. See section 'RINEX Editing & QC' in the documentation for 
 examples on how to call BNC from command line in 'no window' mode for RINEX 
@@ -756,6 +756,6 @@
 <li>File 'FeedEngine.bnc'<br>
 The purpose of this configuration is to feed a real-time GNSS engine with 
-observations from a remote reference stations. The configuration pulls a single 
-stream from an Ntrip Broadcasters. It would of course be possible to pull 
+observations from remote reference stations. The configuration pulls a single 
+stream from an Ntrip Broadcaster. It would of course be possible to pull 
 several streams from different casters. Incoming observations are decoded, 
 synchronized and output through a local IP port and saved into a file. Failure 
