Fix: typos, wording

1 files changed, 3 insertions, 7 deletions

diff --git a/ci-arch.mdwn b/ci-arch.mdwn
index 0a7ccfb..4a528d6 100644
--- a/ci-arch.mdwn
+++ b/ci-arch.mdwn
@@ -158,7 +158,7 @@ future CI system.
   our developers so that they can use CI/CD productively. Acceptance
   criteria: our developers can use CI productively, after given a
   short, 1-page tutorial on how to specify build instructions for
-  their software. FIXME: This might not be very clear; suggetions
+  their software. FIXME: This might not be very clear; suggestions
   welcome.
 
 * **SELFSERVE** Must support self-serve CI, meaning we don't block
@@ -426,11 +426,10 @@ items.
   patch that caused a particular problem with a Selenium test.
 
 * **DEPLOYWHEREVER** Would be nice to have a mechanism for
-  deployment to staging, production, pypi, packagist, toollabs. We
+  deployment to staging, production, toollabs. We
   could do with a way to deploy to any of several possible
   environments, for various use cases, such as bug repoduction, manual
-  exploratory testing, capacity testing, and production. FIXME: what
-  do pypi and packagist do in the list?
+  exploratory testing, capacity testing, and production.
 
 * **MATRIXBUILDS** Would be nice to have efficient matrix builds.
 
@@ -756,9 +755,6 @@ conceptual roles will probably still be there.
 
 ## Credentials management and access control
 
-* FIXME: This is unclear as yet, the text below is some incoherent
-  preliminary rambling by Lars which needs review and fixing.
-
 Credentials and other secrets are needed to allow access to servers,
 services, and files. They are highly security sensitive data. The CI
 system needs to protect them, but allow controlled use of them.