Skip to content

Commit

Permalink
Typos
Browse files Browse the repository at this point in the history
  • Loading branch information
wllm-rbnt committed Feb 18, 2016
1 parent c532ee4 commit 73adfbf
Show file tree
Hide file tree
Showing 3 changed files with 3 additions and 3 deletions.
2 changes: 1 addition & 1 deletion FAQ
Expand Up @@ -59,7 +59,7 @@ Q3. Why can't I see any Forban while using the Wireless network?
To discover Forban, there is a simple discovery service looking
for specific broadcast packet in IPv4 and multicast packet in IPv6.
Some Wireless network are blocking those packets between wireless
clients. You must allow broadcast and/or multicast paquet on your
clients. You must allow broadcast and/or multicast packets on your
Wireless access-point.

Q4. I can see Forban in the interface but it can't copy any files?
Expand Down
2 changes: 1 addition & 1 deletion README
Expand Up @@ -68,7 +68,7 @@ the equal sign being replaced by an exclamation mark.

The opportunistic mode and shared used all the REQUIRED components of
the protocol. The only difference is the lack of automatic file fetching
in the shared mode. The shared mode is usally used on fixed node content
in the shared mode. The shared mode is usually used on fixed node content
where the opportunistic fetching is not desired (e.g. a fixed bookshelf).

The opportunistic mode is working as a simple gossip (or epidemic) protocol
Expand Down
2 changes: 1 addition & 1 deletion README.md
Expand Up @@ -104,7 +104,7 @@ the equal sign being replaced by an exclamation mark.

The opportunistic mode and shared mode use all the REQUIRED components of
the protocol. The only difference is the lack of automatic file fetching
in the shared mode. The shared mode is usally used in a fixed node content
in the shared mode. The shared mode is usually used in a fixed node content
where the opportunistic fetching is not desired (e.g. a fixed bookshelf).

The opportunistic mode works as a simple gossip (or epidemic) protocol
Expand Down

0 comments on commit 73adfbf

Please sign in to comment.