Minro doc fixes (#91)

- Use 'container' instead of 'docker' in the docs
- Wordsmith 'configuration as data'

Author: frankfarzan

README.md

@@ -31,11 +31,10 @@ can be run as pre-commit or post-commit steps to validate configurations before
 
 ### Why KPT Functions
 
-- **Configuration is data:** Many configuration tools conflate data with the operations on that
+- **Configuration as data:** Many configuration tools conflate data with the operations on that
   data (e.g. YAML files embedding a templating language).
   As configuration becomes complex, it becomes hard to read and understand.
-  Our design philosophy is to separate _human-readable data_ from the _state-less programs_ that
-  manipulate that data. We call these programs _functions_.
+  Our design philosophy is to keep configuration as data, which enables us to programmatically manipulate it using stateless programs called _functions_.
 - **Unix philosophy:** Functions should be small, reusable, and composable.
   By implementing the [Configuration Functions Specification][spec],
   we can develop an ever-growing catalog of useful, interoperable functions.

docs/concepts.md

@@ -6,7 +6,7 @@ At a high level, a function can be conceptualized like so:
 
 ![function][img-func]
 
-- `FUNC`: A program, packaged as a docker container, that performs CRUD (Create, Read, Update,
+- `FUNC`: A program, packaged as a container, that performs CRUD (Create, Read, Update,
   Delete) operations on the input.
 - `input`: A Kubernetes List type containing objects to operate on.
 - `output`: A Kubernetes List type containing the resultant Kubernetes objects.

docs/develop.md

@@ -7,7 +7,7 @@ This guide will walk you through developing a KPT function using the Typescript
 - [Setup](#setup)
 - [Create the NPM package](#create-the-npm-package)
 - [Implement the function](#implement-the-function)
-- [Build and push Docker image](#build-and-push-docker-image)
+- [Build and push container images](#build-and-push-container-images)
 - [Use the SDK CLI](#use-the-sdk-cli)
 - [Next Steps](#next-steps)
 
@@ -59,8 +59,7 @@ package discussed in the [Quickstart](develop-quickstart.md) and skip to [implem
 
 #### Using a `kind` Cluster
 
-The easiest way to get developing is to use `kind` to bring up a local cluster, running in a docker
-container.
+The easiest way to get developing is to use `kind` to bring up a cluster running in a local container.
 
 1. Download the [kind binary][download-kind] version 0.5.1 or higher
 1. Use this config file:
@@ -172,7 +171,7 @@ code .
 In `src/my_func.ts`, implement the `KptFunc` interface [documented here][api-kptfunc].
 
 Take a look at [these example functions][demo-funcs] to better understand how to use
-`kpt-functions` library. These functions are available as docker images documented in the [catalog][catalog].
+`kpt-functions` library. These functions are available as container images documented in the [catalog][catalog].
 
 Once you've written some code, build the package with:
 
@@ -193,9 +192,9 @@ To run the tests, use:
 npm test
 ```
 
-## Build and push Docker image
+## Build and push container images
 
-With your working function in-hand, it's time to package your function into an executable docker
+With your working function in-hand, it's time to package your function into an executable container
 image.
 
 `docker build` also requires authentication to GitHub, via the aforementioned credentials:
@@ -204,13 +203,13 @@ image.
 cp ~/.npmrc .
 ```
 
-To build the docker image:
+To build the container image:
 
 ```sh
 npm run kpt:docker-build
 ```
 
-You can now run the image as a docker container, e.g.:
+You can now run the function container, e.g.:
 
 ```sh
 docker run gcr.io/kpt-functions-demo/my-func:dev --help
@@ -227,7 +226,7 @@ You'll need proper authentication/authorization to push to your registry.
 `kpt:docker-push` pushes to the registry specified in the `kpt.docker_repo_base` field in `package.json`.
 You can manually edit this field at any time.
 
-The default value for the docker image tag is `dev`. This can be overridden using`--tag` flag:
+The default value for the container image tag is `dev`. This can be overridden using`--tag` flag:
 
 ```sh
 npm run kpt:docker-build -- --tag=latest
@@ -249,16 +248,16 @@ These sub-commands are available:
 ```console
 kpt:docker-create       Generate Dockerfiles for all functions. Overwrite
                         files if they exist.
-kpt:docker-build        Build docker images for all functions.
-kpt:docker-push         Push docker images to the registry for all functions.
+kpt:docker-build        Build container images for all functions.
+kpt:docker-push         Push container images to the registry for all functions.
 kpt:function-create     Generate stubs for a new function. Overwrites files
                         if they exist.
 kpt:type-create         Generate classes for core and CRD types. Overwrite
                         files if they exist.
 ```
 
 Flags are passed to the CLI after the `--` separator. For example, to pass a tag
-when building a docker image:
+when building a container image:
 
 ```console
 npm run kpt:docker-build -- --tag=latest

docs/run.md

@@ -6,7 +6,7 @@ After completing the [Development Guide](develop.md), you'll have a function tha
 node dist/my_func_run.js --help
 ```
 
-or as a docker container:
+or as a container:
 
 ```sh
 docker run gcr.io/kpt-functions-demo/my-func:dev --help
@@ -231,11 +231,11 @@ You should see labels added to `Namespace` configuration files:
 git status
 ```
 
-#### Understanding Docker Flags
+#### Understanding `docker run` Flags
 
-- `-u`: By default, docker containers run as a non-privileged user. Privileged actions, like
+- `-u`: By default, containers run as a non-privileged user. Privileged actions, like
   filesystem access or calls to the network, require escalated access. Note the example usages of
-  `read-yaml`, which include `docker run -u $(id -u)`, running docker with your user ID.
+  `read-yaml`, which include `docker run -u $(id -u)`, running the container with your user ID.
 - `-v`: Filesystem access requires mounting your container's filesystem onto your local
   filesystem. For example, the `read-yaml` command includes the following: `-v $(pwd):/source`. This connects
   the container's `/source` directory to the current directory on your filesystem.
@@ -245,7 +245,7 @@ git status
 
 Functions can be piped to form sophisticated pipelines.
 
-First, grab the `example-configs` directory and pull the docker images:
+First, grab the `example-configs` directory and pull the container images:
 
 ```sh
 git clone --depth 1 [email protected]:GoogleContainerTools/kpt-functions-sdk.git

go/README.md

@@ -4,7 +4,7 @@
 make
 ```
 
-## Publish docker images
+## Publish container images
 
 ```console
 make publish-functions

ts/create-kpt-functions/src/cli.ts

@@ -50,7 +50,7 @@ async function main() {
     help: dockerCreateHelp,
   });
 
-  const dockerBuildHelp = 'Build docker images for all functions.';
+  const dockerBuildHelp = 'Build container images for all functions.';
   const db = subparsers.addParser('docker-build', {
     addHelp: true,
     description: dockerBuildHelp,
@@ -61,7 +61,7 @@ async function main() {
     help: 'Docker tag used for all function images.',
   });
 
-  const dockerPushHelp = 'Push docker images to the registry for all functions.';
+  const dockerPushHelp = 'Push container images to the registry for all functions.';
   const dp = subparsers.addParser('docker-push', {
     addHelp: true,
     description: dockerPushHelp,