Fix typos

_faq/004_how_to_write_a_proposal.md

@@ -9,5 +9,5 @@ We have some notes you should keep in mind for your proposal:
 * Get in touch with the mentors mentioned in this idea to get into this topic and get answers to your questions.
 * Define - maybe together with the mentor - some measurable milestones, so you can design a rough timetable.
 * Refine and break down your milestones (maybe into stories), also together with the mentor.
-* Try to estimate what stories you can work on within the GSoC period. Please keep in mind that we have 3 kinds of projects: large with 350 hours, medium with 175 hours andi small with 90 hours over 10 weeks.
+* Try to estimate what stories you can work on within the GSoC period. Please keep in mind that we have 3 kinds of projects: large with 350 hours, medium with 175 hours and small with 90 hours over 10 weeks.
 * Use our application template to introduce yourself and describe your project. The resulting document you should upload to the Google Summer of Code program website.

_projects/change_ssid_when_servers_not_accessible.md

@@ -22,7 +22,7 @@ mentors:
     github: smoe
 requirements:
 - Communication skills to discuss best implementation
-- An overview on how mordern UNIX works 
+- An overview on how modern UNIX works
 - Talent to understand the current code base
 tags:
 - tag 1

_projects/completed_elrepo.io.implement_testing_and_features.md

@@ -3,7 +3,7 @@ name: "ElRepo.io implement features and unit testing"
 desc: "Implement various features to elRepo.io"
 requirements:
  - "Flutter knowledge"
- - "RetroShare basic knowledge and c++ will be apreciated"
+ - "RetroShare basic knowledge and c++ will be appreciated"
 difficulty: "medium"
 size: "175 hours"
 status: completed

_projects/completed_evernet_tx-power-control_in_WiFi_networks.md

@@ -1,6 +1,6 @@
 ---
 name: "TX-Power Control in WiFi Networks"
-desc: "Implement per Packet Transmission Power Control for Mediathek and Atheros WiFI chips in OpenWrt"
+desc: "Implement per Packet Transmission Power Control for Mediatek and Atheros WiFI chips in OpenWrt"
 collaborating_projects:
   - openwrt.org
 developers_involved:

_projects/completed_freifunk-call-a-friend.md

@@ -35,17 +35,17 @@ Meshenger users exchange a name, crypto keys and IP/MAC address via QR-Code and
 This App was quite a success and is available on [F-Droid](https://f-droid.org/en/packages/d.d.meshenger/).
 
 Since back then a few features (cryptography, call list, block list, lots of bugfixes) were added. But there was never a release, since calling is broken/fragile in the development branch. The reason is unknown.
-Meshenger is for the most part the [WebRTC Android example](https://chromium.googlesource.com/external/webrtc/+/refs/heads/main/examples/androidapp/) with added features. This should give you a solid guidline.
+Meshenger is for the most part the [WebRTC Android example](https://chromium.googlesource.com/external/webrtc/+/refs/heads/main/examples/androidapp/) with added features. This should give you a solid guideline.
 
-The task for this project would be to fix the the current state (possibly up- or downgrading WebRTC) to get a new release out of the door. A highly motivated person might event want to switch the project to Kotlin. The mentor(s) will support with understanding the code and inner working of the App throughout the project.
+The task for this project would be to fix the current state (possibly up- or downgrading WebRTC) to get a new release out of the door. A highly motivated person might event want to switch the project to Kotlin. The mentor(s) will support with understanding the code and inner working of the App throughout the project.
 
 This is an effort to create something that can be used across the globe for many small communities.
 
 Many aspects of this project are up for the discussion. If you are interested, but unsure, then feel free to contact the mentor(s) beforehand. It is welcome and shows initiative ([email protected]). :-)
 
 #### Milestones
 
-##### GSoC Peraration/Bonding
+##### GSoC Preparation/Bonding
 
 * Let's talk about the current state of project.
 * Talking about the outline of the project.

_projects/completed_irdest-basic-android-app.md

@@ -46,7 +46,7 @@ re-write, with the goal of becoming long-term contributors to the
 project.
 
 The Irdest application architecture uses an RPC protocol to connect
-client to a persistant server that handles user, message, and network
+client to a persistent server that handles user, message, and network
 abstractions.  In order to access these from Android code, some
 bindings in Java (or Kotlin) need to be created
 

_projects/completed_libremesh-easen-trying-it-out.md

@@ -1,6 +1,6 @@
 ---
 name: "Try LibreMesh without having a router"
-desc: "Ease the installation of a virtual environemt to try libremesh out"
+desc: "Ease the installation of a virtual environment to try libremesh out"
 requirements:
  - "Knowledge or interest in containerization an virtualization tools, such as docker"
 difficulty: "medium"
@@ -48,5 +48,5 @@ As of today, LibreMesh nodes can be set up in a virtual environment using QEMU a
 ##### GSOC 2022 FINAL
 
 * Adding entry "Try it out" to libremesh.org web site.
-* Continuous Integration to keep newcommers using latest released versions. 
+* Continuous Integration to keep newcomers using latest released versions.
 * Document what can be done with the virtual network.

_projects/completed_libremeshautomationmonitoring.md

@@ -36,7 +36,7 @@ collaborating_projects:
  - "LibreMesh"
 ---
 
-Create a set of automated tasks to install services on a Raspberry Pi to meet the needs of small community-network with an administration/tech team, e.g. a set of commonly needed monitoring tools, such as Prometheus, Prometheus-node-exporter, Blackbox-exporter, Altermanager, Grafana, VPN and an editing map service.
+Create a set of automated tasks to install services on a Raspberry Pi to meet the needs of small community-network with an administration/tech team, e.g. a set of commonly needed monitoring tools, such as Prometheus, Prometheus-node-exporter, Blackbox-exporter, Alertmanager, Grafana, VPN and an editing map service.
 
 Similar projects or packages:
 https://gitlab.com/librerouter/miniserver

_projects/completed_openwrt-device-page.md

@@ -30,7 +30,7 @@ collaborating_projects:
 ---
 
 Create overview of OpenWrt supported devices to simplify user choice of
-aquicreing new devices.
+acquiring new devices.
 
 #### Milestones
 

_projects/completed_openwrt_ppa.md

@@ -34,7 +34,7 @@ tags:
   - Makefiles
 ---
 
-[OpenWrt](openwrt.org) is a Linux distribution for off the shelf WiFi routers. People who want to make and distribute their personal packages, often for development purposes. So far the best option is to build the whole firmware from zero, but very few people use the OpenWrt SDKs. The idea behind this project is to create a platform to build and host those personal package repositories, possibility integrated with GIT farms, so that the end users can add a repositiory URL to use those packages, modelled on what Ubuntu PPA (Personal Package Archive) has been provided for years.
+[OpenWrt](openwrt.org) is a Linux distribution for off the shelf WiFi routers. People who want to make and distribute their personal packages, often for development purposes. So far the best option is to build the whole firmware from zero, but very few people use the OpenWrt SDKs. The idea behind this project is to create a platform to build and host those personal package repositories, possibility integrated with GIT farms, so that the end users can add a repository URL to use those packages, modelled on what Ubuntu PPA (Personal Package Archive) has been provided for years.
 
 There is no such platform at the moment, packages are made via Pull Requests on a central repository, but that does not meet the requirements of a typical developer, which are:
 

_projects/completed_openwrtppa.md

@@ -32,7 +32,7 @@ tags:
   - Makefiles
 ---
 
-[OpenWrt](openwrt.org) is a Linux distribution for off the shelf WiFi routers. People who want to make and distribute their personal packages, often for development purposes. So far the best option is to build the whole firmware from zero, but very few people use the OpenWrt SDKs. The idea behind this project is to create a platform to build and host those personal package repositories, possibility integrated with GIT farms, so that the end users can add a repositiory URL to use those packages, modelled on what Ubuntu PPA (Personal Package Archive) has been provided for years.
+[OpenWrt](openwrt.org) is a Linux distribution for off the shelf WiFi routers. People who want to make and distribute their personal packages, often for development purposes. So far the best option is to build the whole firmware from zero, but very few people use the OpenWrt SDKs. The idea behind this project is to create a platform to build and host those personal package repositories, possibility integrated with GIT farms, so that the end users can add a repository URL to use those packages, modelled on what Ubuntu PPA (Personal Package Archive) has been provided for years.
 
 There is no such platform at the moment, packages are made via Pull Requests on a central repository, but that does not meet the requirements of a typical developer, which are:
 

_projects/completed_retroshare-webui.md

@@ -39,11 +39,11 @@ The  Web interface is made in Javascript and uses Retroshare automated JSON API
 internals of libretroshare. It already has its own building system and already works, although it is rather incomplete.
 
 The work in this project consists in developing the remaining Javascript code to complete the Web interface, which
-includes the configuration panel, the access to channels, forums and boards, as well as the handlign of GXS identities.
-A plus would also be to add a pannel for statistics, showing various aspects of the internal variables of file transfer,
+includes the configuration panel, the access to channels, forums and boards, as well as the handling of GXS identities.
+A plus would also be to add a panel for statistics, showing various aspects of the internal variables of file transfer,
 GXS synchronisation, so that the software can easily be run on a headless server.
 
-Although this project is fairly easy, it requires some reasonnable knowledge of JS. The project do not aim to changing
+Although this project is fairly easy, it requires some reasonable knowledge of JS. The project do not aim to changing
 the current framework the Web interface is based on, nor its internal algorithmics. There is no specific order in which the
 different aspects of the Web interface can be covered by the candidate. A proof of involvement (a few commits fixing
 simple issues) will be requested in order to select motivated applicants.

_projects/completed_retroshareWebUI.md

@@ -41,7 +41,7 @@ Missing components are the following:
 ##### PREPARATION/BONDING
 
 * get familiar with the Retroshare network
-* understand how GXS works. A white paper is available here: https://hal.inria.fr/hal-01617423
+* understand how GXS works. A white paper is available here: https://inria.hal.science/hal-01617423
 * discuss possible options with the developers
-* we only recruit applicants who made relevants pull requests to the project before the selection period begins. Ask the devs ([email protected]) for the key to the dev Tor node, and meet them in the dev forum/chat *before* the project application period starts.
+* we only recruit applicants who made relevant pull requests to the project before the selection period begins. Ask the devs ([email protected]) for the key to the dev Tor node, and meet them in the dev forum/chat *before* the project application period starts.
 

_projects/completed_traffic_monitoring_and_classification.md

@@ -47,7 +47,7 @@ The goal of this project is, to realize traffic monitoring and classification me
 
 * Analysis of different approaches to run XDP and eBPF on OpenWrt devices
 * Integration of the tools and drivers into OpenWrt
-* Design of a moonitoring environment that builds upon the approaches of XDP and eBPF
+* Design of a monitoring environment that builds upon the approaches of XDP and eBPF
 * Description of different use cases that leverage the capabilities of XDP/eBPF on OpenWrt devices
 * Implementation of a dedicated use case that demonstrates the benefits of the XDP/eBPF
 
@@ -58,8 +58,8 @@ The goal of this project is, to realize traffic monitoring and classification me
 
 ##### Coding Period
 
-* Evaluation of XDP/eBPF on different hardwarew plattforms such as x86, ARM, and MIPS
-* Implementation of different XDP and eBPF approches
-* Implementation of differnet user space tools as loader
+* Evaluation of XDP/eBPF on different hardware platforms such as x86, ARM, and MIPS
+* Implementation of different XDP and eBPF approaches
+* Implementation of different user space tools as loader
 * Evaluation of the use case such as exporting a traffic matrix for further analysis
 * Demonstration of the benefits

_projects/completed_videoodyssee-refactoring.md

@@ -84,7 +84,7 @@ There are already some ideas for improvements:
 
 Get in touch with us to talk about potential projects we can derive from this idea. You're also invited to check out the software projects and try to get them running.
 
-You are free to define the scope with your proposal, so it will be possible to do that project as a full-time (350 hours) or a hafl-time(175 hours) project. It is also possible to split that idea up into several projects.
+You are free to define the scope with your proposal, so it will be possible to do that project as a full-time (350 hours) or a half-time(175 hours) project. It is also possible to split that idea up into several projects.
 
 ### Community bonding
 

_projects/freifunkgoes100G.md

@@ -69,6 +69,6 @@ Accordingly, the goal of this project is to port Freifunk/OpenWrt [6] OS to the
 
 ##### Coding Period
 
-* Porting Meallanox Switch with Sectrum II chipset to OpenWrt
+* Porting Mellanox Switch with Sectrum II chipset to OpenWrt
 * Add dedicated Mellanox target to the Freifunk/OpenWrt device set
 * Evaluation 100G SFP+ fiber ports

_projects/googlecoralboardsupport.md

@@ -43,7 +43,7 @@ Accordingly, the participant will first integrate the board into the OpenWrt env
 
 * [1] https://coral.ai/products/pcie-accelerator
 * [2] https://openwrt.org/
-* [3] http://trac.gateworks.com/wiki/TPU
+* [3] https://trac.gateworks.com/wiki/TPU
 * [4] https://coral.ai/docs/edgetpu/models-intro
 
 

_projects/libremesh-cable-purpose-autodection.md → _projects/libremesh-cable-purpose-autodetection.md

@@ -1,7 +1,7 @@
 ---
-name: "LibreMesh Cable Purpose Autodection"
+name: "LibreMesh Cable Purpose Autodetection"
 desc: "For the router to detect if you are connecting a client, another router, an internet connection, and to configure itself accordingly at runtime"
-markdown: libremesh-cable-purpose-autodection.md
+markdown: libremesh-cable-purpose-autodetection.md
 collaborating_projects:
   - libremesh
   - altermundi

_projects/libremeshpiranianewrelease.md

@@ -24,9 +24,9 @@ issues:
 size: 350 hours # choose between 90 hours, 175 hours and 350 hours
 markdown: libremeshpiranianewrelease
 mentors:
-- name: Bruno Viana
+- name: Bruno Vianna
   contact:
-    github: brunoviana  # provide at least one contact option
+    github: brunovianna  # provide at least one contact option
     email: [email protected]
     other_chat_options:
     - link to matrix or similar
@@ -41,10 +41,10 @@ tags:
 
 After the publication of the  [New Pirania API](https://github.com/libremesh/lime-packages/pull/893), a lot has been gained with Pirania in Libremesh.
 Many communities could be used and even today they use it as a very important tool for the collection of funds, for the payment of the provider and sometimes even for people who work.
-Everbody can manage the sistem with [Pirania UI](https://github.com/libremesh/lime-app/pull/329).
-each router has access to the Captive Portal system and this makes it be distributed and extremely used in a community and of different types of governance. Pirania has diferent options of governance, this means that each community can understand the best use that it can make with the system and different cases of use.
+Everybody can manage the system with [Pirania UI](https://github.com/libremesh/lime-app/pull/329).
+each router has access to the Captive Portal system and this makes it be distributed and extremely used in a community and of different types of governance. Pirania has different options of governance, this means that each community can understand the best use that it can make with the system and different cases of use.
 but for it to be more complete it is important to raise the different ideas that have already been [raised by the community](https://github.com/libremesh/lime-packages/issues/76).
-And after the latest versions of lime-packages, pirania is not included, mainly because the basis of pirania's operation is the iptbles rules contained in ./usr/bin/captive-portal. As iptables ends up creating a very large file, the new version of libremesh decided to migrate from iptables to nftables.
+And after the latest versions of lime-packages, pirania is not included, mainly because the basis of pirania's operation is the iptables rules contained in ./usr/bin/captive-portal. As iptables ends up creating a very large file, the new version of libremesh decided to migrate from iptables to nftables.
 This and other changes need to be made to fit pirania into a new release.
 
 
@@ -67,4 +67,4 @@ This and other changes need to be made to fit pirania into a new release.
 ##### GSOC FINAL
 
 * review everything and present it to the libremesh community to more contributions.
-* Documentation
+* Documentation

_projects/retrosharevoip.md

@@ -41,7 +41,7 @@ This project can be a "175 hours" project for a sufficiently skilled developer.
 
 #### Milestones
 
-* find a suitable cross-plaform video codec
+* find a suitable cross-platform video codec
 * handle auto-adjustment of bandwidth for video/sound with proper priority handling to avoid gaps
 * implement proper GUI device selection and notifications
 

_projects/retrosharewallplugin.md

@@ -57,7 +57,7 @@ This is to be discussed with the developers.
 ##### PREPARATION/BONDING
 
 * get familiar with the Retroshare network
-* understand how GXS works. A white paper is available here: https://hal.inria.fr/hal-01617423
+* understand how GXS works. A white paper is available here: https://inria.hal.science/hal-01617423
 * discuss possible options with the developers
 * we only recruit applicants who made relevant pull requests to the project before the selection period begins. Ask for the key to the dev Tor node ([email protected]) and meet the devs in the dev forum/chat rooms.
 

_projects/transmit_power_control_algorithm_for_modern_wifi_chips.md

@@ -48,7 +48,7 @@ The goal of this project is to initially implement a novel TPC algorithm in the
 ##### GSOC COMMUNITY BONDING
 
 * Develop foundational understanding of the importance for resource allocation in wireless transmission, with a specific focus on power control.
-* Familize with the tools for developing and analzying resource control algorithms in user space
+* Familiarize with the tools for developing and analyzing resource control algorithms in user space
 * Create visual representation detailing the architecture of the formulated TPC algorithm.
 
 ##### GSOC MIDTERM

_projects/voctowebsplitcontentandlogic.md

@@ -40,7 +40,7 @@ tags:
 
 Voctoweb is the software behind media.ccc.de and used for distributing video recordings of a lot of events. We forked their repo to set up our own video portal, [media.freifunk.net](https://media.freifunk.net). As there was only one user of this software for years, content pages and templates are mixed with the business logic.
 
-Goal of this project should be: We're able to set up a new instance of voctoweb and add our own contents, designs, templates and other customizations. When the projects is finished we have a document on how to get your own, independant and customized instance.
+Goal of this project should be: We're able to set up a new instance of voctoweb and add our own contents, designs, templates and other customizations. When the projects is finished we have a document on how to get your own, independent and customized instance.
 
 It may be hard to split the original project in a first step. But if we find a way to make it easy for others to customize the installation, that doesn't matter.
 

partials/tabs/students.html

@@ -7,7 +7,7 @@
     <div class="col m8 offset-m2">
       <h1 class="fine center">Hello World!</h1>
       <h4 class="light center">
-       The students who've participted in Google Summer of Code with {{ site.organization }}
+       The students who've participated in Google Summer of Code with {{ site.organization }}
       </h4>
     </div>
   </div>