Rename Elafros to Knative in community. (#1041)

* Rename "Elafros" to "Knative" in community docs.

* Update code-of-conduct address to separate from maintainers address.

code-of-conduct.md

@@ -56,7 +56,7 @@ further defined and clarified by project maintainers.
 
 Instances of abusive, harassing, or otherwise unacceptable behavior
 may be reported by contacting the project team at
-knative-[email protected].com. All complaints will be reviewed
+knative-code-of-conduct@googlegroups.com. All complaints will be reviewed
 and investigated and will result in a response that is deemed
 necessary and appropriate to the circumstances. The project team is
 obligated to maintain confidentiality with regard to the reporter of

config/config-logging.yaml

@@ -18,7 +18,7 @@ metadata:
   name: config-logging
   namespace: knative-serving-system
 data:
-  # Common configuration for all Elafros codebase
+  # Common configuration for all Knative codebase
   zap-logger-config: |
     {
       "level": "info",

sample/autoscale/sample.yaml

@@ -36,7 +36,7 @@ spec:
         # This is the Go import path for the binary to containerize
         # and substitute here.
         image: github.com/knative/serving/sample/autoscale
-        # When scaling up Elafros controller doesn't have a way to
+        # When scaling up Knative controller doesn't have a way to
         # know if the user container is good for serving.  Having a
         # readiness probe prevents traffic to be routed to a pod
         # before the user container is ready.