summaryrefslogtreecommitdiff
path: root/community/gsoc/project_ideas/tcp_ip_stack.mdwn
diff options
context:
space:
mode:
authorCarl Fredrik Hammar <hammy.lite@gmail.com>2010-03-10 16:19:06 +0100
committerCarl Fredrik Hammar <hammy.lite@gmail.com>2010-03-10 16:19:06 +0100
commit6eb6d5314e303379debbef82921a215ef2b00d98 (patch)
tree55536b9636dc3ccfaf7829c96940774a13cf49e3 /community/gsoc/project_ideas/tcp_ip_stack.mdwn
parent5a615978181a1b8d85326d8cf3137ed4b0b46bf7 (diff)
Fix typos and spelling on GSoC pages
Diffstat (limited to 'community/gsoc/project_ideas/tcp_ip_stack.mdwn')
-rw-r--r--community/gsoc/project_ideas/tcp_ip_stack.mdwn2
1 files changed, 1 insertions, 1 deletions
diff --git a/community/gsoc/project_ideas/tcp_ip_stack.mdwn b/community/gsoc/project_ideas/tcp_ip_stack.mdwn
index b56bff51..735c8bbb 100644
--- a/community/gsoc/project_ideas/tcp_ip_stack.mdwn
+++ b/community/gsoc/project_ideas/tcp_ip_stack.mdwn
@@ -21,7 +21,7 @@ more flexibly. Rather than just having the standard socket interface, plus some
lower-level hooks for special needs, there are explicit (perhaps
filesystem-based) interfaces at all the individual levels; special application
can just directly access the desired layer. All kinds of packet filtering,
-routing, tunneling etc. can be easily achieved by stacking compononts in the
+routing, tunneling etc. can be easily achieved by stacking components in the
desired constellation.
Implementing a complete modular network stack is not feasible as a GSoC