Get rid of some whitespace

Author: aliok

docs/eventing/samples/writing-receive-adapter-source/01-theory.md

@@ -86,7 +86,7 @@ func NewController(ctx context.Context, cmw configmap.Watcher) *controller.Impl
 
 Sample source's [`update-codegen.sh`](https://github.com/knative/sample-source/blob/master/hack/update-codegen.sh) have the configuration
 to have the required things above generated and injected:
-```bash 
+```bash
 # Generation
 ${CODEGEN_PKG}/generate-groups.sh "deepcopy,client,informer,lister" \
   knative.dev/sample-source/pkg/client knative.dev/sample-source/pkg/apis \

docs/eventing/samples/writing-receive-adapter-source/05-receive-adapter.md

@@ -25,7 +25,7 @@ func main() {
 ## Defining NewAdapter implementation and Start function
 The adapter's `pkg` implementation consists of two main functions;
 
-1. A `NewAdapter(ctx context.Context, aEnv adapter.EnvConfigAccessor, ceClient cloudevents.Client) adapter.Adapter {}` call, which creates the 
+1. A `NewAdapter(ctx context.Context, aEnv adapter.EnvConfigAccessor, ceClient cloudevents.Client) adapter.Adapter {}` call, which creates the
 new adapter with passed variables via the `EnvConfigAccessor`. The created adapter will be passed the cloudevents client (which is where the events are forwarded to). This is sometimes refered
 to as a sink, or `ceClient` in the Knative ecosystem.  The return value is a reference to the adapter as defined by the adapter's local struct.
 

docs/eventing/samples/writing-receive-adapter-source/07-eventing-contrib.md

@@ -5,13 +5,13 @@ weight: 10
 type: "docs"
 ---
 
-If you would like to contribute Knative's [`eventing-contrib`](https://github.com/knative/eventing-contrib/), as a starting point you can 
-have a look at different sources there, such as  
-[`KafkaSource`](https://github.com/knative/eventing-contrib/tree/master/kafka/source), 
-[`GithubSource`](https://github.com/knative/eventing-contrib/tree/master/github) and 
+If you would like to contribute Knative's [`eventing-contrib`](https://github.com/knative/eventing-contrib/), as a starting point you can
+have a look at different sources there, such as
+[`KafkaSource`](https://github.com/knative/eventing-contrib/tree/master/kafka/source),
+[`GithubSource`](https://github.com/knative/eventing-contrib/tree/master/github) and
 [`AWSSQSSource`](https://github.com/knative/eventing-contrib/tree/master/awssqs).
 
-To generate and inject `clientset`, `cache`, `informers`, and `listers`, ensure that the specific source subdirectories has been added to the injection portion of the 
+To generate and inject `clientset`, `cache`, `informers`, and `listers`, ensure that the specific source subdirectories has been added to the injection portion of the
 [`hack/update-codegen.sh`](https://github.com/knative/eventing-contrib/blob/master/hack/update-codegen.sh) script.
 
 ```patch

docs/eventing/samples/writing-receive-adapter-source/README.md

@@ -11,16 +11,16 @@ well as receive adapter, which events can be viewed through a basic
 Just want to see the code? The reference project is
 [https://github.com/knative/sample-source](https://github.com/knative/sample-source).
 
-A variety of event sources are available in Knative [`eventing-contrib](https://github.com/knative/eventing-contrib/) such as 
-[`KafkaSource`](https://github.com/knative/eventing-contrib/tree/master/kafka/source), 
-[`GithubSource`](https://github.com/knative/eventing-contrib/tree/master/github) and 
-[`AWSSQSSource`](https://github.com/knative/eventing-contrib/tree/master/awssqs) that can be used as a reference.  
+A variety of event sources are available in Knative [`eventing-contrib](https://github.com/knative/eventing-contrib/) such as
+[`KafkaSource`](https://github.com/knative/eventing-contrib/tree/master/kafka/source),
+[`GithubSource`](https://github.com/knative/eventing-contrib/tree/master/github) and
+[`AWSSQSSource`](https://github.com/knative/eventing-contrib/tree/master/awssqs) that can be used as a reference.
 
 ## Other ways
 
 With the approach in this tutorial, you will create a CRD and a controller for the event source which makes it reusable.
 
-You can also write your own event source using a [ContainerSource](../../../eventing/sources/README.md#meta-sources) which 
+You can also write your own event source using a [ContainerSource](../../../eventing/sources/README.md#meta-sources) which
 is an easy way to turn any dispatcher container into an Event Source. Similarly, another option is using [SinkBinding](../../../eventing/sources/README.md#meta-sources)
 which provides a framework for injecting environment variables into any Kubernetes resource which has a `spec.template` that looks like a Pod (aka PodSpecable).
 
@@ -31,7 +31,7 @@ The target audience is already familiar with Kubernetes and Go development and
 wants to develop a new event source, importing their custom events via Knative
 Eventing into the Knative system.
 
-This tutorial is for having your event source in an independent repository. 
+This tutorial is for having your event source in an independent repository.
 If you would like to contribute Knative's [`eventing-contrib`](https://github.com/knative/eventing-contrib/) and have your source
 there, there are some instructions at [Adding the event source to `eventing-contrib`](./07-eventing-contrib.md).