From 829dbf1a13d1a1ef4d99f3bf4ef17d29b2722997 Mon Sep 17 00:00:00 2001 From: error Date: Sat, 29 Oct 2022 11:25:43 +0200 Subject: [PATCH] fix typos --- content/pages/credits.md | 2 +- content/pages/privacy.md | 2 +- content/posts/scroip.md | 6 +++--- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/content/pages/credits.md b/content/pages/credits.md index 16d4ed9..5d7414d 100644 --- a/content/pages/credits.md +++ b/content/pages/credits.md @@ -11,7 +11,7 @@ It's licensed under the [GNU Affero General Public License v3.0](https://www.gnu ## LATEX.css -This site's template is based on [LATEX.css](https://latex.now.sh "LaTeX.css"), a CSS library that makes a website look like a LaTeX document. +This site's template is based on [LATEX.css](https://latex.now.sh "LaTeX.css"), a CSS library that makes a website look like a LATEX document. LATEX.css is licensed under the MIT License. The template can be found [here](https://git.undefinedbehavior.de/undef/undefined-pelican-theme "Undefined Pelican Theme"). diff --git a/content/pages/privacy.md b/content/pages/privacy.md index b93339d..0e0de54 100644 --- a/content/pages/privacy.md +++ b/content/pages/privacy.md @@ -12,4 +12,4 @@ Personal data is discarded once the request was served. This server only serves requests via HTTPS. All communication is end-to-end encrypted with TLS. Requests received on port 80 (HTTP) are redirected to port 443 (HTTPS). -If you're interested in more information on how this webside is delivered to your device, have a look at [RFC 9112](https://datatracker.ietf.org/doc/html/rfc9112 "HTTP/1.1") for HTTP/1.1 and [RFC 8446](https://datatracker.ietf.org/doc/html/rfc8446 "The Transport Layer Security (TLS) Protocol Version 1.3") for TLS 1.3. +If you're interested in more information on how this website is delivered to your device, have a look at [RFC 9112](https://datatracker.ietf.org/doc/html/rfc9112 "HTTP/1.1") for HTTP/1.1 and [RFC 8446](https://datatracker.ietf.org/doc/html/rfc8446 "The Transport Layer Security (TLS) Protocol Version 1.3") for TLS 1.3. diff --git a/content/posts/scroip.md b/content/posts/scroip.md index cd12817..0b451d5 100644 --- a/content/posts/scroip.md +++ b/content/posts/scroip.md @@ -11,8 +11,8 @@ License: CC-BY-NC When I was a child, I used to play a lot with my slot car racing track. After stumbling upon it again recently, I started wondering if I could build something to control it over the network. Not that I needed a remote control for it, but it seemed like a fun project. -However, simply creating an API that offers precise control over the device seemed way to straight forward - the controlling mechanism itself should add its challenges. -So I came up with the idea to control it with the traffic itself. +However, simply creating an API that offers precise control over the device seemed way too straight forward - the controlling mechanism itself should add its challenges. +So I came up with the idea to control it with the network traffic itself. The more traffic is sent to the remote control, the faster the car is supposed to go.[°Use more bandwidth!!!] ## Reversing @@ -21,7 +21,7 @@ In order to build the remote control, the first step was to figure out how the s ![Simplified circuit diagram for a slot car racing system]({static}/posts/scroip/carrera.svg "Simplified circuit diagram of a slot car racing system") -The underlying mechanism is fairly simple. The power supply provides about 14.8 V DC voltage, which is used to power the car's motor. +The underlying mechanism is fairly simple. The power supply provides about 14.8 V DC voltage, which is used to power the car's engine. The speed of the car is controlled by a variable resistor within the controller, which allows to control the voltage the car receives. Pushing the controller further down lowers the resistance, which raises the voltage available to the car and makes is go faster. A third wire is used to brake the car when the controller is in its neutral position by utilizing the current generated by the motor when the car is rolling out.