Fix typos found by crate-ci/typos

Author: jplatte

blog/_posts/2019-10-16-finance.adoc

@@ -44,7 +44,7 @@ The current scheme for payouts is as follows:
 * the final arrangement is made public
 
 The biggest weakness of this scheme is that the decision quorum is not well-balanced.
-We hope to overcome this issue by being transparent and tweaking the descision process if it doesn't work well.
+We hope to overcome this issue by being transparent and tweaking the decision process if it doesn't work well.
 
 We also need to pay taxes from the money we receive via Open Collective.
 The VAT is 19%, but donations from EU-based companies are exempt from VAT.
@@ -57,7 +57,7 @@ So, the final formula for the yearly budget looks like this:
 (cost * 10/8 payouts * 119/100 VAT * 108/100 transaction fee) * 12
 ----
 
-Pluggin the costs from above, we get the following budget targets:
+Plugging in the costs from above, we get the following budget targets:
 
 **52050 EUR / Year**: I dedicate half of my time for rust-analyzer, 20% of the budget is spend funding people outside of Ferrous Systems.
 

blog/_posts/2020-02-11-2019-financial-report.adoc

@@ -12,7 +12,7 @@ We've rounded that number up to 10000 (using some funds from this year) and spli
 * 20% for contributors, not affiliated with Ferrous
 
 Ferrous share went to paying for part of https://github.com/matklad[@matklad]'s time (thats me!), and for administrative tasks.
-The remaining 2000 EUR were payed to https://github.com/flodiebold[@flodiebold] for implementing and maintaining type inference infrastructure of rust-analyzer.
+The remaining 2000 EUR were paid to https://github.com/flodiebold[@flodiebold] for implementing and maintaining type inference infrastructure of rust-analyzer.
 
 Our biggest Open Collective sponsors in 2019 were:
 

blog/_posts/2020-04-20-first-release.adoc

@@ -142,7 +142,7 @@ Extend selection kbd:[Shift+Alt+->]::
 This is again a feature which is relatively simple to implement, but a huge helper.
 It progressively selects larger and larger expressions, statements and items.
 It works exceptionally well in combination with multiple cursors.
-One hidden capability of this feature is a navigation help: if you are in a middle of a function, you can get to the beginning of it by extending seleciton several times, and then pressing kbd:[<-].
+One hidden capability of this feature is a navigation help: if you are in a middle of a function, you can get to the beginning of it by extending selection several times, and then pressing kbd:[<-].
 
 video::/assets/blog/first-release/extend-selection.webm[options="autoplay,loop",width=100%]
 

blog/_posts/2020-05-18-next-few-years.adoc

@@ -187,7 +187,7 @@ One wrinkle here is that rustc test suite at the moment consists predominantly o
 Such a test suite is ideal for testing conformance and catching regressions, but is not really well suited for rapid TDD.
 I think we should make an effort to build a unit test suite a-la rust-analyzer, such that it's easy, for example, to test name resolution without building the type checker, and which doesn't require stdlib.
 
-== Scaling Maintainance
+== Scaling Maintenance
 
 Finally, all changes here represent deep cuts into an existing body of software.
 Pushing such ambitious projects to completion require people, who can dedicate significant amounts of their time and energy.

blog/_posts/2020-09-16-challeging-LR-parsing.adoc

@@ -115,7 +115,7 @@ So, here's
 Design error _resilient_ (and not just error _recovering_) LR parsing algorithm.
 
 Note that error resilience is a topic orthogonal to error reporting.
-I haven't payed much attention to error reporting (in my experience, synchronous reporting of syntax errors in the editor compensates for bad syntax error messages), but it might be the case that MCRS are a good approach to there.
+I haven't paid much attention to error reporting (in my experience, synchronous reporting of syntax errors in the editor compensates for bad syntax error messages), but it might be the case that MCRS are a good approach to there.
 
 == Expressions Grammar
 
@@ -191,7 +191,7 @@ Implement LSP server which provides basic IDE features, as well as live preview.
 
 == Challenge Responses
 
-Folks fom https://galois.com/[Galois] develop a classy-named https://github.com/GaloisInc/daedalus[DaeDaLus] -- a flexible data description language for generating parsers with data dependencies.
+Folks from https://galois.com/[Galois] develop a classy-named https://github.com/GaloisInc/daedalus[DaeDaLus] -- a flexible data description language for generating parsers with data dependencies.
 DaeDaLus makes an impressive attempt at solving the second challenge.
 The language is powerful enough to just
 https://github.com/GaloisInc/daedalus/blob/fe088fefc553e37974b47345a1da4b49a10da7f7/bin-exp/pratt-bin-expr.ddl#L53-L69[directly encode]

blog/_posts/2020-09-28-how-to-make-a-light-bulb.adoc

@@ -127,7 +127,7 @@ Django web framework has a nice pattern to implement this -- function based view
 ----
 
 def my_form(request):
-  ctx = fetch_stuff_from_postgress()
+  ctx = fetch_stuff_from_postgres()
   if request.method == 'POST':
     # apply changes ...
   else:

blog/_posts/2023-12-26-the-heart-of-a-language-server.adoc

@@ -257,7 +257,7 @@ There are two properties of the underlying languages which make this approach wo
 
 1. Syntactic nesting must match semantic nesting.
    Looking at parent's sibling makes sense only if the current element should be among the siblings.
-2. Getting sematic element for an entire file is trivial.
+2. Getting semantic element for an entire file is trivial.
 
 The second one is actually less true in Rust than it is in Kotlin or C#!
 In those languages, each file starts with a package declaration, which immediately mounts the file at the appropriate place in the semantic model.

thisweek/_posts/2020-02-03-changelog-10.adoc

@@ -14,7 +14,7 @@ Release: release:2020-02-03[]
 == Fixes
 
 * pr:2933[] don't compute diagnostics on the main thread.
-  That fixes a long-standing issue with peformance degradation due to `cargo check`.
+  That fixes a long-standing issue with performance degradation due to `cargo check`.
 * pr:2810[] make magical search of struct literals work in more contexts.
 * pr:2916[] fix slow `cargo check` performance due to unbuffered reads.
 * pr:2924[] avoid spawning more than one Cargo for `cargo check`.

thisweek/_posts/2020-03-02-changelog-14.adoc

@@ -32,7 +32,7 @@ image::https://user-images.githubusercontent.com/1711539/75685982-c56a8480-5c9b-
 * pr:3355[] add completion & docs for `featureFlag` configuration in VS Code extension.
 * pr:3309[] look for `Cargo.toml` not only in the root and parent directory, but also among one-level child directories.
 * pr:3387[] type inference for slice patterns.
-* pr:3397[] add minimal metatdata to VS Code extension.
+* pr:3397[] add minimal metadata to VS Code extension.
 
 == Fixes
 

thisweek/_posts/2020-03-09-changelog-15.adoc

@@ -18,7 +18,7 @@ image::https://user-images.githubusercontent.com/906069/76160803-92a60d80-612d-1
 +
 image::https://user-images.githubusercontent.com/1711539/76219227-cd837080-6215-11ea-8d0d-a9447b1d26b1.gif[]
 +
-Insertion of snippets is controled by `completion.insertion.add-argument-snippets` feature flag.
+Insertion of snippets is controlled by `completion.insertion.add-argument-snippets` feature flag.
 
 * pr:3498[] when completing function call, trigger parameter hints automatically.
 * pr:3500[] more concise mode for parameter hints: