Typo and language fixes from Vivek

1 files changed, 13 insertions, 13 deletions

diff --git a/negotiation.mdwn b/negotiation.mdwn
index 33694c8..a5332b3 100644
--- a/negotiation.mdwn
+++ b/negotiation.mdwn
@@ -20,7 +20,7 @@ from time to time. Luckily, that's what I'm good at, and
 patience is part of my job. "These guys are flush. They just
 got a ton of VC money last week. They're also desperate.
 Their whole current product line is broken, and not likely
-to survive another security catastrophy. If we play our
+to survive another security catastrophe. If we play our
 cards right, we can earn enough of a fee to cover our
 salaries for several months."
 
@@ -60,7 +60,7 @@ of us accept it. Deal?"
 
 That's a thing we established when we set up a company with
 Robin. We're contractors, and while that means we have to
-accept clients and client projects, both ¤obin and I have
+accept clients and client projects, both Robin and I have
 plenty of experience working for unpleasant people. Every
 new job, and every new client, brings a new group of people
 who need to be taught basics of software development
@@ -75,7 +75,7 @@ I get nods from everyone, except Robin. She looks thoughtful
 for a few moments, and looks around the table at everyone,
 then finally also nods. Everyone stands up and leaves the
 conference room to continue their day. We're between paying
-projects, so there's practice runs and stdying and
+projects, so there's practice runs and studying and
 experimentation with new tools going on. I stay, to finish
 the meeting minutes for our internal wiki, and to send an
 email to Sam at SmartHomes, Inc, the prospective customer,
@@ -200,7 +200,7 @@ No, he was upset, but controlling himself. He stopped the
 shaking by forming fists with his hands. His knuckles were
 white. He was breathing slowly, deliberately, and deeply.
 
-"I can't I'm happy to hear this, of course."
+"I can't say I'm happy to hear this, of course."
 
 "Would you like to discuss possible ways in which we can
 deal with this and find ways in which we can work together?"
@@ -223,7 +223,7 @@ is that both sides can trust and respect each other. On our
 side, we can't be productive if we feel we're not treated
 well, or if we can't be blunt when that's needed. On your
 side, if you don't trust us to deliver, there's no point in
-tolerating our excentricities or us challenging you to do
+tolerating our eccentricities or us challenging you to do
 better."
 
 "We don't believe in blind trust, so our standard contract
@@ -245,7 +245,7 @@ but those are only important if you insist on us working
 from your premises."
 
 "I'm sure we can have a product owner. The practical details
-can surely be arranged, but we would like to have on our
+can surely be arranged, but we would like to have you on our
 premises. It's easier if we can talk in person, than doing
 everything over email or video calls."
 
@@ -298,7 +298,7 @@ acceptable in modern times.
 "Based on this short black-box evaluation, and pending
 discussion with your techies, my initial suggestion is that
 you need a completely new platform for you next generation
-products, one that's built to be secure and updatebele. We
+products, one that's built to be secure and updateable. We
 have that. You also need processes for preparing and
 distributing updates to you users, and to take on the
 reponsibility of providing the updates. We can help with
@@ -319,7 +319,7 @@ help with that too."
 ------------------------------------------------------------
 
 Robin, Nina, and I are at the SmartHome, Inc, headquarters, in a
-large, lavish board room. Mahongany walls, a large oval table, comfy,
+large, lavish board room. Mahogany walls, a large oval table, comfy,
 well-padded leather chairs, a huge monitor, and power, network, and
 display sockets in the desk surface at every seat. All three of us are
 plugged in, and prepared to give a talk to the senior techies about
@@ -328,7 +328,7 @@ what we offer to do for them. This could go either really well, or
 really badly. We've decided for a strategy of shock and awe.
 
 The SmartHome techies arrive in three clusters, and seat themselves in
-the opposite end of the table from us. Most of them seem sundued, with
+the opposite end of the table from us. Most of them seem subdued, with
 a couple of exceptions, who mostly seem belligerent.
 
 I nod at Nina, who opens her laptop and starts typing. I stand up and
@@ -394,7 +394,7 @@ animation. Nina stands still. "I just did."
 old guy clearly doesn't believe what Nina is saying. He shakes his
 head.
 
-"First, I'm inside your firewall, rememher. My laptop is on your guest
+"First, I'm inside your firewall, remember. My laptop is on your guest
 wifi. The wifi password is printed in the wall. It's just like
 vampires. Firewalls do not help when you keep inviting people into
 your home. Second, while your gadgets indeed do have a password, and
@@ -413,7 +413,7 @@ controls locks, and heating. Shall we ask her to open the locks and
 turn the heat down?"
 
 The SmartHome techies mumble variations of "yeah". I shake my head.
-"No. One you has to stand up and politely ask Nina to do those thing.
+"No. One of you has to stand up and politely ask Nina to do those thing.
 Alternatively you can take back control of your office in some way.
 But you have to do it from this board room. Remember, the doors are
 locked."
@@ -456,7 +456,7 @@ is 'iabasaisfa', which is short for 'I am bad at security and I should
 feel bad'. All lower case."
 
 The SmartHomers being now properly cowed, I walk the through the rest
-of my presentation, which is the same things I told Sam at the cafe,
+of my presentation. It covers the same stuff I told Sam at the cafe,
 except dressed up with fonts and stock photos. We have a reasonable
 discussion, and they admit all their faults.
 
@@ -595,7 +595,7 @@ portaserver?"
 The portaserver is another of Nina's builds. It's like the mini-rack,
 but has normal servers, which we use to run continuous integration
 services, version control, a wiki, an IRC server, and so on. We have
-one that power our office infrastructure, and because it's portable,
+one that powerss our office infrastructure, and because it's portable,
 when a project requires us to work somewhere else, we can bring it
 with us. This again saves us a ton of trouble. Instead of convincing
 customer IT to give us access to their servers, for example, we just