From 0283329e1a7d48e45f1c7fdbf3d8ef7f5fe4b5b9 Mon Sep 17 00:00:00 2001 From: MartinFarrent Date: Thu, 24 May 2012 23:29:16 -0700 Subject: [PATCH] Updated Running a public or community server (markdown) --- Running-a-public-or-community-server.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Running-a-public-or-community-server.md b/Running-a-public-or-community-server.md index 9f3e810..7039a48 100644 --- a/Running-a-public-or-community-server.md +++ b/Running-a-public-or-community-server.md @@ -12,7 +12,7 @@ For instance, registration policy is affected by these differences. If you run a On the other hand, if you had a _community_ server that allowed people from anywhere to sign up, you'd quickly run out of resources and your site would eventually grind to a halt. That's because a community server probably knows how many users it will have and can purchase resources accordingly - a soccer club, for instance, has a defined membership base. -A public server will either have to upgrade frequently, or keep an eye on it's resources carefully to know when to stop accepting sign ups. +A public server will either have to upgrade frequently, or keep an eye on it's resources carefully to know when to stop accepting sign ups. It is perfectly acceptable for a listed public server to be closed to new registrations if resources are running low. ***The technical environment - operating system***