spelling fixes from rczlonka
This commit is contained in:
parent
3a03baf1de
commit
81b59a6205
|
@ -75,8 +75,8 @@ Servers which do not understand the Ping activity will hopefully ignore it.
|
|||
|
||||
-- usage
|
||||
|
||||
It is unspecified how one initiaties a ping, but it is expected to be a manual
|
||||
operation performed by a system adminstrator. This will generate traffic,
|
||||
It is unspecified how one initiates a ping, but it is expected to be a manual
|
||||
operation performed by a system administrator. This will generate traffic,
|
||||
which may then be logged. The admin reads the logs and solves the problem.
|
||||
Specific problem solving instructions are not provided here.
|
||||
|
||||
|
|
|
@ -57,7 +57,7 @@ Such explanation would be less necessary were the tables not misused for
|
|||
multiple purposes. Will probably split them apart again soon.
|
||||
|
||||
Note that some logical seeming joins won't work. The honker column of honks
|
||||
does not have a correspondng entry in the honkers table, since we frequently
|
||||
does not have a corresponding entry in the honkers table, since we frequently
|
||||
receive messages from people we don't follow. Should we track everybody whose
|
||||
identity crosses our path? This seems unnecessary. The honkers table is more
|
||||
like a mapping of active relationships, not a directory of all peoples.
|
||||
|
|
Loading…
Reference in New Issue