fix: english:

g

1 files changed, 8 insertions, 8 deletions

diff --git a/content/bsd/history/01_multics.md b/content/bsd/history/01_multics.md
index b926552..3e18afe 100644
--- a/content/bsd/history/01_multics.md
+++ b/content/bsd/history/01_multics.md
@@ -16,14 +16,14 @@ abstract = "BSD history starts with Multics"
 ## Origins of time-sharing {#origins-of-time-sharing}
 
 Let's start our journey back when dinosaurs roamed the earth, engineers wore ties, and Barbie was first gaining popularity - the 60s.
-Nowadays, we are accused to companies selling devices with a loss, as all the money comes from software subscriptions.
+Nowadays, we have grown accustom to companies selling devices at lower profit margins - with most profit coming from software subscriptions.
 But 70 years ago it was the complete opposite.
 Companies bought expensive computers, huge machines, and what was running on them was of lesser value.
 And I really mean _expensive_.
 An IBM System/360 Model 20, presented in 1964, could have been bought starting from USD 62,710 (USD 622,626 adjusted for inflation) or rented for USD 1280 (USD 12,708 adjusted)[^fn:1].
 Sellers earned a lot from the devices.
 But, naturally, companies making all those investments wanted a nice return.
-This led to creation of _time-sharing_.
+This led to the creation of _time-sharing_.
 
 {{< img-c "ibm-360.jpg" "https://www.nbcnews.com/tech/gadgets/5-reasons-love-mad-mens-new-star-ibm-360-n101716" >}}
 IBM 360 in an official photoshoot.
@@ -31,15 +31,15 @@ IBM 360 in an official photoshoot.
 
 This concept seems natural now: multiple processes were able to share computer resources, so multiple applications could run at the same time.
 Applications could even run for different users.
-Ergo, time-sharing allowed for multi-user multitasking processing.
+Ergo, time-sharing allowed for multi-user multitask processing.
 This is in stark contrast to batch-processing, where only a single program would be able to compute at any particular time.
 An example of such processing would be EDSAC, the first electronic computer[^fn:2].
 I won't go into detail of time-sharing, but you can read more in "Time sharing in large computers", C. Strachey, 1959.
 But what is important here is how it was used.
 All computation happened on a single, large server.
-End users would use _computer terminals_ which were _multiplexed_ into that server, called _mainframe_.
+End users would use _computer terminals_ which were _multiplexed_ into that server, called a _mainframe_.
 What is multiplexing you ask?
-Simply said, it's a way to different combine signals into a shared medium.
+Simply said, it's a way to combine different signals into a shared medium.
 It was used extensively for land-line telephony, where all signals were transferred over shared wires.
 
 {{< img-c "edsac.jpg" "https://www.datacenterdynamics.com/en/analysis/rebuilding-edsac-the-first-real-computer/" >}}
@@ -52,9 +52,9 @@ EDSAC, the "first computer".
 Let's jump to 1969.
 
 _Multics (MULTiplexed Information and Computing)_ was an early time-sharing operating system developed by _MIT_, _General Electrics_ and _Bell Labs_.
-It pioneered many of innovations which are still widely used in computing systems of today: hierarchical file system, redirection as interprocess communication, or the existence of a shell[^fn:3], as well as memory pages, memory protection, or the ability for a single machine to use multiple CPUs and memory[^fn:4].
-It was however also huge, both in terns of memory usage (the resident kernel could occupy a huge part of memory living not enough for applications) and code size (it consisted of about 1,5k source modules)[^fn:3].
-_Multics_ was experimental and therefore ambitious, complex, and designed by trial and error.
+It pioneered many of innovations which are still widely used in the computing systems of today: hierarchical file system, redirection as interprocess communication, or the existence of a shell[^fn:3], as well as memory pages, memory protection, or the ability for a single machine to use multiple CPUs and memory[^fn:4].
+It was however also huge, both in terms of memory usage (the resident kernel could occupy a huge part of memory living not enough for applications) and code size (it consisted of about 1,5k source modules)[^fn:3].
+_Multics_ was experimental and therefore ambitious, complex - designed by trial and error.
 It was delivered late, early on had performance problems, and in 1969 _Bell Labs_ withrew from the project[^fn:5].
 
 {{< img-c "multics-login.png" "https://en.wikipedia.org/wiki/Multics#/media/File:Multics-Login.png" >}}