You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@openwhisk.apache.org by ra...@apache.org on 2020/08/24 17:18:37 UTC

[openwhisk] branch master updated: fix deploy description in readme (#4947)

This is an automated email from the ASF dual-hosted git repository.

rabbah pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/openwhisk.git


The following commit(s) were added to refs/heads/master by this push:
     new 433376a  fix deploy description in readme (#4947)
433376a is described below

commit 433376a7963ff60724611776e4745ebc0d913117
Author: Matt Welke <ma...@gmail.com>
AuthorDate: Mon Aug 24 13:18:21 2020 -0400

    fix deploy description in readme (#4947)
---
 docs/actions-go.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/actions-go.md b/docs/actions-go.md
index 6a6009a..ddf7f8b 100644
--- a/docs/actions-go.md
+++ b/docs/actions-go.md
@@ -73,9 +73,9 @@ The runtime `action-golang-v1.11` accepts:
 - executable binaries in Linux ELF executable compiled for the AMD64 architecture
 - zip files containing a binary executable named `exec` at the top level, again a Linux ELF executable compiled for the AMD64 architecture
 - a single source file in Go, that will be compiled
-- a zip file not containing in the top level a binary file `exec`, it will be interpreted as a collection of zip files, and compiled
+- a zip file not containing in the top level a binary file `exec`, it will be interpreted as a collection of source files in Go, and compiled
 
-You can create a binary in the correct format on any GO platform cross-compiling with `GOOS=Linux` and `GOARCH=amd64`. However it is recommended you use the compiler embedded in the Docker image for this purpose using the precompilation feature, as described below.
+You can create a binary in the correct format on any Go platform cross-compiling with `GOOS=Linux` and `GOARCH=amd64`. However it is recommended you use the compiler embedded in the Docker image for this purpose using the precompilation feature, as described below.
 
 ## Using packages and vendor folder