Update: about page

1 files changed, 23 insertions, 23 deletions

diff --git a/about.mdwn b/about.mdwn
index 2bf5882..07d6bc2 100644
--- a/about.mdwn
+++ b/about.mdwn
@@ -1,41 +1,41 @@
 [[!meta title="About ick"]]
 
-[[!img ick-logo.svg]]
-
 Ick is a system for continuous interation or CI.
 
-Why yet another CI system?
-=============================================================================
-
-**Ick** aims to become a system that's less hassle to set up or
-operate or keep running than any other publically available
-self-hosted system, without compromising correctness or security.
+**Why yet another CI system?** Ick aims to become a system that's less
+hassle to set up or operate or keep running than any other publically
+available self-hosted system, without compromising correctness or
+security.
 
-See [[origin|blog/2017/10/10/origin]] for a description of how Ick got
-started.
+See the [[origin|blog/2017/10/10/origin]] story for a description of
+how ick got started.
 
 
 Manifesto
 =============================================================================
 
-Continuous integration (CI) is powerful tool for software development.
-It should not be tedious, fragile, or annoying. It should be quick and
-simple to set up, and work quietly in the background unless there's a
-problem in the code being built and tested.
+Continuous integration (CI) is powerful and necessary tool for modern
+software development. It should not be tedious, fragile, or annoying.
+It should be quick and simple to set up, and work quietly in the
+background unless there's a problem in the code being built and
+tested.
 
 A CI system should be simple, easy, clear, clean, scalable, fast,
-comprehensible, transparent, reliable, and boost your productivity to
-get things done. It should not be a lot of effort to set up, require a
-lot of hardware just for the CI, need frequent attention for it to
-keep working, and developers should never have to wonder why something
-isn't working.
+comprehensible, transparent, reliable, and boost your productivity for
+getting things done. It should not be a lot of effort to set up,
+require a lot of hardware just for the CI, need frequent attention for
+it to keep working, and operations and developers people should never
+have to wonder whether and why something isn't working.
 
 A CI system should be flexible to suit your build and test needs. It
 should support multiple types of workers, as far as CPU architecture
-and operating system version are concerned.
+and operating system version are concerned. It should be able to build
+any kind of project, against any kind of target.
 
 Also, like all software, CI should be fully and completely free
-software and your instance should be under your control.
+software and your instance should be under your control. If you don't
+want to host it yourself, you should have access to a hosted version
+as well.
 
-(Ick is nothing of this yet, but it will try to become all of it. In
-the best _possible_ taste.)
+Ick is nothing of this yet, but it will try to become all of it. In
+the best _possible_ taste.