summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorLars Wirzenius <liw@liw.fi>2017-01-08 11:38:28 +0200
committerLars Wirzenius <liw@liw.fi>2017-01-08 11:38:28 +0200
commit28e30e26c8774225c5ea283a0b81bcb980e6eb26 (patch)
tree9ab140b21ac970ce259387bcf4d284ba98524f94
parentc6f0b7883234d146a84408bc5ed8e5cc97ef5579 (diff)
downloadnoir.liw.fi-28e30e26c8774225c5ea283a0b81bcb980e6eb26.tar.gz
Typo fixes from spell checking in Emacs
-rw-r--r--.ikiwiki/indexdbbin9715 -> 9693 bytes
-rw-r--r--negotiation.mdwn20
2 files changed, 10 insertions, 10 deletions
diff --git a/.ikiwiki/indexdb b/.ikiwiki/indexdb
index 6f21d15..0359029 100644
--- a/.ikiwiki/indexdb
+++ b/.ikiwiki/indexdb
Binary files differ
diff --git a/negotiation.mdwn b/negotiation.mdwn
index 0e989c7..c88face 100644
--- a/negotiation.mdwn
+++ b/negotiation.mdwn
@@ -8,7 +8,7 @@ were considering taking on a new project for a new client.
rejected them last year!" Robin is our architect and lead
developer. She's experienced and by far the most opinionated
of us. After a lifetime of working in software development,
-and being belittled, harrassed, and disrespected by
+and being belittled, harassed, and disrespected by
colleagues, bosses, and everyone else, she's the least
inclined of us to compromise.
@@ -138,7 +138,7 @@ make quality stuff that lasts."
"That is exactly why..." I cut him off. This part is going
to be painful enough without having to hear him explain his
side. "Please, let me explain our issues completely before
-you defend youself. Here is the situation as we understand
+you defend yourself. Here is the situation as we understand
it. You produce a line of gadgets for so called smart homes,
which mean controller, sensors, and displays to automate
parts of the functionality in a home, so that those living
@@ -288,7 +288,7 @@ Sam's shoulders are hanging. His voice seems defeated.
Robin is clearly having a good time now. "It took me only
half an hour to get into a root shell. You have a telnet
port open, and as soon as I figured out that, and googled to
-find a list of you hardcoded root passwords, I was in.
+find a list of you hard-coded root passwords, I was in.
That's 1970s security, it's not nearly acceptable today.
From my research, you also have no upgrade system, so as
soon someone finds a security hole, your users have to buy a
@@ -301,7 +301,7 @@ you need a completely new platform for you next generation
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
+responsibility of providing the updates. We can help with
that, but you'll need to do the bulk of the work. You also
need to port your actual applications to the new platform,
and that's probably not something we can do for you."
@@ -309,7 +309,7 @@ and that's probably not something we can do for you."
"This sounds like you want us to start all over from
scratch. That's going go be a hard sell to our investors."
-I smile an evil smile. "They're going to like bankrutpcy
+I smile an evil smile. "They're going to like bankruptcy
even less. If you want help convincing the investors and
stockholders, or your management or developers, well, we can
help with that too."
@@ -340,7 +340,7 @@ reputation when it comes to quality and security. To confirm this,
I've collected some quotes from recent product reviews, and from
Twitter."
-The audience shifing in their seats. I can see several of them getting
+The audience shifting in their seats. I can see several of them getting
ready to jump to the defence of what they've built, or have had a hand
in building. To keep the upper hand, I tap the keyboard on my laptop,
and my first slide appears on the big monitor, accompanied with Joan
@@ -521,7 +521,7 @@ them. And we need to deliver on our promises. But that's OK. We're The
Team. We're the bitches who keep promises."
Robin nods, and looks around the table. "How about the rest of you?
-Yay or nay?"
+Yea or nay?"
Bertram, the junior developer, isn't sure. "Looks to me like there's
mostly work here for porting our platform to their hardware. I'm
@@ -577,7 +577,7 @@ There's a couple of wifi access points, also fully controlled
remotely. Basically we can program everything so that the devices can
be updated, reset, and generally put through their paces, without
having to have a human push buttons, connect cables, or otherwise
-handle hardware. This becomes importand when the project reaches a
+handle hardware. This becomes important when the project reaches a
phase where we want to verify that the devices survive being
forcefully rebooted by cutting power every few seconds for a week.
Nobody wants to do that by hand. It's a thing Nina built for a project
@@ -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 powerss our office infrastructure, and because it's portable,
+one that powers 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
@@ -607,6 +607,6 @@ The Towel being the name of the office portaserver. It's our third.
The first one, "Moomin", grew old enough to be replaced with a new
generation of hardware. The second one, "Loki", having suffered a
minor accident involving a drop from the third floor, a tank out
-practicing urban warfare, and a squad of very frightened conscripts.
+practising urban warfare, and a squad of very frightened conscripts.
The third generation is rather more shockproof and has "don't panic"
written on each side in large, friendly letters.