[chore] improvements such as typos etc

posts/2024-06-22-haskell-tooling.md

@@ -6,7 +6,7 @@ title: haskell tooling  overview
 
 This is supposed to serve as a summary of available tooling in the haskell ecosystem to make discovery easier. 
 
-This is especially well-suite for beginners who need to get an overview. Every paragraph contains a link to the respecting tool.
+This is especially well-suited as an overview of haskell tooling for beginners. Every paragraph contains a link to the respecting tool.
 
 If you have corrections or additional tools that I should list, please contact me at [contact@mangoiv.com](mailto:contact@mangoiv.com).
 
@@ -24,7 +24,7 @@ Documentation on how to use the `GHC`, can be found in the [user's guide](https:
 
 ### 2.1 cabal
 
-While ghc supports `make`, the ubiquitous build tool for haskell programs is [`cabal`](https://cabal.readthedocs.io/en/stable/). Most Haskell 
+The ubiquitous build tool for haskell programs is [`cabal`](https://cabal.readthedocs.io/en/stable/). Most Haskell 
 software is packaged with `cabal`. You can recognise this from the presence of the `*.cabal` file in the project.
 
 If you start a haskell project, cabal is generally the recommended choice.
@@ -54,7 +54,8 @@ infrastructure but the general takeaway is that you should probably not use it i
 The same goes for [`bazel`](https://rules-haskell.readthedocs.io/en/latest/). It is one of the few tools that don't use `cabal`. It has its own `DSL` for writing packages
 but it brings a large amount of complexity which you probably don't want to opt-in to if you don't already have a usecase.
 
-Haskell projects can also be built with `make`. You should probably not do that though, if you don't have good reasons.
+There have been people who built Haskell projects with shake and make but as far as I am aware that doesn't happen much these days and you 
+probably should not if you do not have good reasons.
 
 ## 3. installers for haskell tooling
 
@@ -79,7 +80,7 @@ There are also quick-start tools like [`haskell-flake`](https://flake.parts/opti
 
 ### 3.3 stack
 
-stack provides ways to install various tools, including `ghc`. Nowadays, `ghcup` is strictly preferred.
+stack (in addition to its qualities as a package set distributor) provides ways to install various tools, including `ghc`. Nowadays, `ghcup` is strictly preferred.
 
 ### 3.4 others
 
@@ -116,7 +117,8 @@ installed via the `cabal install ghcid` but also with `stack` and `nixpkgs`.
 
 ### 4.4 ghciwatch
 
-[`ghciwatch`](https://github.com/MercuryTechnologies/ghciwatch) is a relatively new alternative to `ghcid` writtin in rust (embarassing), check it out!
+[`ghciwatch`](https://github.com/MercuryTechnologies/ghciwatch) is a relatively new alternative to `ghcid` written in rust (embarassing), check it out, to find 
+whether it is for you / a worthwhile alternative to ghcid. 
 
 ### 4.5 static-ls
 
@@ -167,7 +169,7 @@ konw if they have fixed that since.
 
 #### 6.1.6 weeder
 
-[`weeder`](https://github.com/ndmitchell/weeder) is a haskell tool that can detect dead code for you.
+[`weeder`](https://github.com/ocharles/weeder) is a haskell tool that can detect dead code for you.
 
 ### 6.2. for `.cabal` files