[docs] Documentation on configuring functions runtime#4263
[docs] Documentation on configuring functions runtime#4263jiazhai merged 5 commits intoapache:masterfrom
Conversation
sijie
added
doc
site2/docs/functions-runtime.md
Outdated
|
|
||
| ## Configure Kubernetes runtime | ||
|
|
||
| Configuring Kubernetes runtime is as simple as configuring the other two runtimes. You can just uncomment |
There was a problem hiding this comment.
What's the meaning of "uncomment"?
There was a problem hiding this comment.
:) try google it. @jennifer88huang
https://www.google.com.hk/search?newwindow=1&safe=strict&ei=-9PYXJWHEPKwmAWSqZdQ&q=uncomment&oq=uncomment&gs_l=psy-ab.3..0i10i70i255j0i10l3j0i67j0l5.1725.1725..2054...0.0..0.104.104.0j1......0....1..gws-wiz.t1uIqcWY1uA
There was a problem hiding this comment.
@jiazhai Thank you very much for your information. I'll pay attention to my word usage next time.
When you ''uncomment" sth in code, you actually want to enable some configuration options; in some cases, you just disable it with "comment", that's why we use comment lines in code. Here I want to tell @sijie, he could use "enable" / "disable" or other similar words to replace "uncomment"/"comment" in technical writing. When he explains the meaning, he will realize it.
There was a problem hiding this comment.
@jennifer88huang I think from technical writing perspective, "enabling" and "disabling" are probably better. However sometimes "enabling" and "disabling" are too general that users have no idea to enable or disable. Can we use a phrase like "enabling sth by uncommenting ..."?
There was a problem hiding this comment.
Sure, it's much better.
|
run integration tests |
|
run java8 tests |
|
run java8 tests |
|
run java8 tests |
1 similar comment
|
run java8 tests |
|
run integration tests |
4 participants
Fixes #4171
Fixes #3073