Made terminology more consistent

README.md

@@ -3,13 +3,14 @@
 [![code style: prettier](https://img.shields.io/badge/code_style-prettier-ff69b4.svg?style=flat-square)](https://github.com/prettier/prettier)
 
 WeeRT consists of three, independent parts:
-- A real-time logging and display server, written in Javascript and running on [Node](https://nodejs.org/en/). This
+- The WeeRT uploader. This is a [WeeWX service](http://weewx.com/docs/customizing.htm#The_weeWX_service_architecture), 
+which arranges for your data to be uploaded from WeeWX to the WeeRT server.
+- The WeeRT server, a real-time logging and display server, written in Javascript and running on 
+[Node](https://nodejs.org/en/), using the [Express framework](https://expressjs.com/). This
 server listens for real-time data updates from WeeWX, then archives them in
 an [InfluxDB](https://www.influxdata.com/time-series-platform/influxdb/) database. It also acts
-as a webserver for the WeeRT client (below).
-- A WeeWX uploader. This is a [WeeWX service](http://weewx.com/docs/customizing.htm#The_weeWX_service_architecture),
-running on WeeWX, which arranges for your data to be uploaded to the WeeRT server.
-- A client, written in Javascript using [React](https://reactjs.org/) and [Redux](https://redux.js.org/).
+as a webserver for the WeeRT client.
+- The WeeRT browser client, written in Javascript using [React](https://reactjs.org/) and [Redux](https://redux.js.org/).
 It runs in a browser and interacts with the WeeRT server.
 
 ![WeeRT architecture](./weert_architecture.jpg)