Updated Running a public or community server (markdown)

Running-a-public-or-community-server.md

@@ -60,7 +60,7 @@ After choosing the right environment and installing Friendica, you need to do so
 
 8. _Block multiple registrations_: This stops users creating a second account with the same email address to be used as a community forum/page, or a second personal account.  If you're trying to maximise resources, limit your users to one account each, and disallow the creation of forum pages.  Pages are lower in resources than user accounts by a long way, but they soon add up if you've got a lot of them.
 
-9._ OpenID support_: If this option is turned on, users will be able to create an account and log in using their OpenID. Warning: Depending on providers, this may not work with mixed SSL policies.
+9. _ OpenID support_: If this option is turned on, users will be able to create an account and log in using their OpenID. Warning: Depending on providers, this may not work with mixed SSL policies.
 
 10. _Full Name Check_: This will ensure users enter what looks like a full name - actually, any two words 'look' like a full name to the system. What this is really for is stopping bots creating spam accounts. Leave it turned off unless you have a problem with bots.
 
@@ -82,19 +82,19 @@ After choosing the right environment and installing Friendica, you need to do so
 
 19. _Only allow Friendica contacts_: Exactly what it says on the tin - users can only add other Friendica contacts. No Diaspora, Ostatus, RSS, or email. Just Friendica.  This is wonderful for resources, you'll save a lot.  Community servers should really consider this option. However, if you're hosting a _public_ server, the chances are you doing so to help the project - and that your members will still want their Diaspora and Facebook contacts.  Not using this option is a sacrifice, but probably one worth paying in the long term.
 
-20. _Global Directory Update URL_: This is the URL of the global directory you would like members of your site who opt in to be listed in the global directory to use. There is only one global directory at the moment. Either leave the field as it is, or leave it blank to disable profiles being submitted to the local directory.
+20. _Global Directory Update URL_: If members of your site opt to be listed in a global directory, this is the one that will be used. Actually, there is only one global directory at the moment. Either leave the field as it is, or leave it blank to disable profiles being submitted to the global directory.
 
-21. Verify SSL. This turns on strict SSL checking, which will make your site check it's communicating with sites using certificate authority SSL certificates. This means sites using self-signed SSL certificates will not be able to connect to your site.  This might arguably be a good thing.  Self-signed SSL certificates will generate warnings that users just don't understand and in many cases, make them leave immediately.  On the other hand, you'll miss out on some perfectly good contacts who refuse to bow to the SSL cartel, even with a free certificate from StartSSL.  If I had to make the call?  Unless you really know what you're doing, or you have particular security concerns, leave this unselected.
+21. _Verify SSL_: This turns on strict SSL checking, which will make your site check it's communicating with sites using certificate-authority SSL certificates. This means sites using self-signed SSL certificates will not be able to connect to your site.  This might arguably be a good thing.  Self-signed SSL certificates will generate browser warnings that users just don't understand and sometimes even make them leave immediately.  On the other hand, you'll miss out on some perfectly good contacts who refuse to bow to the SSL cartel - and chances are that the problem is alleviated anyway if these contacts use the respective self-signed SSL policy in Friendica. Unless you really know what you're doing, or you have particular security concerns, leave this unselected.
 
-22. Network Timeout. This is the number of seconds before your server gives up trying to talk to a remote server. Initially, you should leave this value at the default. However, as you get bigger and things get slower, increasing this can reduce timeout errors. Increase it slowly, until people stop complaining of errors, and start complaining of things "taking ages" instead.
+22. _Network Timeout_: This is the number of seconds before your server gives up trying to talk to a remote server. Initially, you should leave this value at the default. However, as you get bigger and things get a bit slower, increasing this can reduce timeout errors. Increase it slowly, until people stop complaining of errors.
 
-23. Delivery interval. This reduces system load by using a delay between background delivery processes. The recommend values as displayed should be used, however, increasing this number slightly can help if you start having problems.  Increase in intervals of one second at a time until things come back under control.
+23. _Delivery interval_: This reduces system load by implementing a delay between background delivery processes. The recommend values as displayed should be used - however, increasing this number slightly can help if you start having problems. Increase in intervals of one second at a time until things come back under control.
 
-24. Poll interval.  As delivery interval, except the delay is applied to background polling processes.  Enter 0 to use the same interval as the delivery processes, as was the case before this option was introduced.
+24. _Poll interval_:  This is like the delivery interval, except that the delay is applied to background polling processes.  Enter 0 to use the same interval as the delivery processes.
 
-25. Maximum Load Average.  This sets the maximum load average before delivery and poll processes are deferred.  If you set this value too low, posts will back up and never be delivered or polled.  Too high and it doesn't offer any relief for your server.  This is a new feature, and has only really been tested by two public servers.  Don't play with it unless you really understand what you're doing or feel you are in a position to be able to experiment.
+25. _Maximum Load Average_:  This sets the maximum load average before delivery and poll processes are deferred.  If you set this value too low, posts will back up and never be delivered or polled.  Too high and it doesn't offer any relief for your server.  This is a new feature, and has only really been tested by two public servers.  Don't play with it unless you really understand what you're doing or feel you are in a position to be able to experiment.
 
-26. Accounts abandoned after x days. This is the most overlooked and most useful weapon in tackling server load.  If you are a public server, most of your users will sign up, enable Facebook, then never return again. After x days, we'll stop polling their Facebook contacts (and other external resources) to save system resources. In many cases, after x days, it's as if they never joined. But as soon as they next log in, things will start working normally again. The smaller this number, the quicker you free up resources, but the more you annoy people who were just away for a few days. Finding the perfect balance between too soon and too late would be to know the users of your particular server perfectly. Since that is impossible, a rule of thumb might be this: 29 days are four weeks of vacation plus a day to sleep off jet lag. That could be a reasonable setting for a community server. If you're running a public server and experience problems, you may wish to reduce this figure to 14.  
+26. _Accounts abandoned after x days_: This is the most overlooked and most useful weapon in tackling server load.  If you are a public server, a lot of your users will sign up, enable Facebook, then never return again. After x days, we'll stop polling their Facebook contacts (and other external resources) to save system resources. In many cases, after x days, it's as if they never joined. But as soon as they next log in, things will start working normally for them again. The smaller this number, the quicker you free up resources, but the more you annoy people who were just away for a few days. Finding the perfect balance between too soon and too late would be to know the users of your particular server perfectly. Since that is impossible, a rule of thumb might be this: 29 days are four weeks of vacation plus a day to sleep off jet lag. That could be a reasonable setting for a community server. If you're running a public server and experience problems, you may wish to reduce this figure to 14.