Make references to example config files more consistent

INSTALL.md

 change references to that to match your host, and generate some passwords for
 `YOURSECRET1` and `YOURSECRET2`.
 
-There are also some complete [example config files](https://www.dropbox.com/sh/jgp4s8kp6xuyubr/5FACgJmqLD) available..
+There are also some complete [example config files](https://www.dropbox.com/sh/jgp4s8kp6xuyubr/5FACgJmqLD) available, mentioned in each section.
 
 ## Install prosody and otalk modules
 ```sh
 ```
 
 ## Configure prosody
-Modify the config file in `/etc/prosody/prosody.cfg.lua`:
+Modify the config file in `/etc/prosody/prosody.cfg.lua` (see also the example config file):
+
 - modules to enable/add: compression, bosh, smacks3, smacks2, carbons, mam, lastactivity, offline, pubsub, adhoc, websocket, http_altconnect
 - comment out: `c2s_require_encryption = true`, and `s2s_secure_auth = false`
 - change `authentication = "internal_hashed"`
 Component "jitsi-videobridge.jitmeet.example.com"
     component_secret = "YOURSECRET1"
 ```
-- check the example config file, next to the document (`prosody.cfg.lua`)
 
 Generate certs for the domain:
 ```sh
 server_names_hash_bucket_size 64;
 ```
 
-Add a new file in /etc/nginx/sites-available (see the jitmeet.example.com file for example)
+Add a new file `jitmeet.example.com` in `/etc/nginx/sites-available` (see also the example config file):
 ```
 server {
     listen 80;
 cd /etc/nginx/sites-enabled
 ln -s ../sites-available/jitmeet.example.com jitmeet.example.com
 ```
-check the example config files for more info.
 
 ## Fix firewall if needed
 ```sh
 mv jitmeet/ jitmeet.example.com
 ```
 
-Edit host names in `/srv/jitmeet.example.com/config.js`:
+Edit host names in `/srv/jitmeet.example.com/config.js` (see also the example config file):
 ```
 var config = {
     hosts: {
     minChromeExtVersion: '0.1' // Required version of Chrome extension
 };
 ```
-check the example config file, next to the document (config.js)
 
 Restart nginx to get the new configuration:
 ```sh