Author: toad Date: 2008-08-01 15:33:19 +0000 (Fri, 01 Aug 2008) New Revision: 21557
Modified: trunk/freenet/src/freenet/l10n/freenet.l10n.en.properties Log: grammar fix Modified: trunk/freenet/src/freenet/l10n/freenet.l10n.en.properties =================================================================== --- trunk/freenet/src/freenet/l10n/freenet.l10n.en.properties 2008-08-01 13:41:29 UTC (rev 21556) +++ trunk/freenet/src/freenet/l10n/freenet.l10n.en.properties 2008-08-01 15:33:19 UTC (rev 21557) @@ -695,8 +695,8 @@ Node.passOpennetPeersThroughDarknetLong=If true, opennet noderefs (NEVER our own darknet noderef) will be relayed through our darknet peers. So a node (this node, or its peers) can get opennet peers from its darknet peers. This is useful because it allows us to bootstrap new opennet peers after having lost our peers due to downtime, for example. However, it may make traffic analysis slightly easier, so turn it off if you are paranoid. Node.port=FNP port number (UDP) Node.portLong=UDP port for node-to-node communications (Freenet Node Protocol) -Node.publishOurPeersLocation=Shall we send our peer's location to our peers? -Node.publishOurPeersLocationLong=Shall we send our peer's location to our peers? Doing so helps routing but gives some information away to a potential attacker. +Node.publishOurPeersLocation=Shall we send our peers' locations to our peers? +Node.publishOurPeersLocationLong=Shall we send our peers' locations to our peers? Doing so helps routing but gives some information away to a potential attacker. Node.routeAccordingToOurPeersLocation=Shall we use the locations of the peers of our peers into account for routing purposes? Node.routeAccordingToOurPeersLocationLong=Shall we use the locations of the peers of our peers into account for routing purposes? Doing so helps routing but might help a potential attacker. Node.storeDirectory=Store directory
