From 19b1ca3a135918d95667af0ddebe315e2c4582ae Mon Sep 17 00:00:00 2001 From: Daniel Berteaud Date: Sat, 14 Mar 2015 13:54:19 +0100 Subject: [PATCH] Doc cleanups --- templates/default/documentation.html.ep | 35 +++++++++++++++++---------------- 1 file changed, 18 insertions(+), 17 deletions(-) diff --git a/templates/default/documentation.html.ep b/templates/default/documentation.html.ep index bb69f8c..3e1f878 100644 --- a/templates/default/documentation.html.ep +++ b/templates/default/documentation.html.ep @@ -39,7 +39,7 @@
  • Text chat (and you can save history)
  • Screen sharing
  • Email invitations
    • -
  • Email notification when someone joins one of your rooms
    • +
  • Email notifications when someone joins one of your rooms
  • Persistent/reserved rooms
  • Chairman functionnalities (mute/pause/kick other peers)
  • Grant chairman role to other peers
    • @@ -49,7 +49,7 @@

    - VROOM is translated in French and English. You're welcome to submit patches or pull requests to enhance localization, or add new ones. + VROOM is available in French and English. You're welcome to submit patches or pull requests to enhance localization, or add new ones.

    @@ -57,20 +57,20 @@ How it works

    - WebRTC allows browsers to browsers direct connections. This allows the best latency as it avoids round trip through a server, + WebRTC allows browsers to browsers direct connections. This provides the best latency as it avoids round trip through a server, which is important with real time communications. But it also ensures the privacy of your communications. VROOM takes advantage of those new WebRTC technologies, and does the following:

    - As long as possible, data channels are established directly between peers, but in some situations, this is not possible. In those case + As long as possible, data channels are established directly between peers, but in some situations, this is not possible (NAT, firewalls etc...). In those case data streams are relayed through a TURN server
    @@ -109,7 +109,7 @@ For the same reason, I recommend running Apache as webserver (others like Nginx probably work too, but I provide configuration sample only for Apache)

    - VROOM can probably with other DB engine (like PostgreSQL) with minor modifications. + VROOM can probably work with other DB engine (like PostgreSQL) with minor modifications. If you're interrested in adding support for other engines, you're welcome to help
    @@ -210,7 +210,7 @@ mysql -uroot vroom < /opt/vroom/docs/database/schema.mysql Two sample apache configurations are provided in the conf directory Copy the config you want in /etc/httpd/conf.d/ @@ -219,8 +219,8 @@ mysql -uroot vroom < /opt/vroom/docs/database/schema.mysql In either case, you might want to adjust the apache configuration
    - The admin interface of VROOM will be available on /vroom/admin (alias) or /admin (vhost) must be protected by your web server. - VROOM provides no authentication at all. In the sample configuration, the access is restriucted to localhost, + The admin interface of VROOM will be available on /vroom/admin (alias) or /admin (vhost) and must be protected by your web server. + VROOM provides no authentication at all. In the sample configuration, the access is restricted to localhost, but you can change this to anything you want

    @@ -286,7 +286,7 @@ cp /opt/vroom/conf/settings.ini.dist /opt/vroom/conf/settings.ini TURN servers will be used by the ICE process. If you plan to use VROOM only on a local network, where each peer can connect to each others, you can just omit this part. But if you want - VROOM to work from anywhere, you'll need use STUN and most likely TURN too. + VROOM to work from anywhere, you'll need use STUN and most likely TURN too.