diff --git a/README.md b/README.md
index 7c7c498..76409ec 100644
--- a/README.md
+++ b/README.md
@@ -13,6 +13,8 @@
:pencil: You can add more questions & answers by submitting pull requests :) You can read more about it [here](CONTRIBUTING.md)
+:cn: You can find the [中文](README-ZH_CN.md) chinese translation right [here](README-zh_CN.md)
+
****
@@ -56,8 +58,6 @@
-[中文 README](README-zh_CN.md)
-
## DevOps
@@ -88,7 +88,7 @@ Each piece of code (change/patch) is verified, to make the change is safe to mer
-What do you consider as best practices for CI/CD?
+What CI/CD best practices are you familiar with? Or what do you consider as CI/CD best practice?
@@ -115,7 +115,7 @@ Each piece of code (change/patch) is verified, to make the change is safe to mer
What are you taking into consideration when choosing a tool/technology?
-You may use one or all of the following:
+In your answer you can mention one or more of the following:
* mature vs. cutting edge
* community size
* architecture aspects - agent vs. agentless, master vs. masterless, etc.
@@ -134,7 +134,7 @@ which follows the immutable infrastructure paradigm.
-What ways are you familiar with to deliver a software?
+What ways are you familiar with to deliver a software? What are the disadvantages of each method?
* Archive - collect all your app files into one archive (e.g. tar) and deliver it to the user.
* Package - depends on the OS, you can use your OS package format (e.g. in RHEL/Fefodra it's RPM) to deliver your software with a way to install, uninstall and update it using the standard packager commands
@@ -197,7 +197,7 @@ One can argue whether it's per company definition or a global one but at least a
-How do you measure your CI/CD quality? Are there any metrics you are using?
+How do you measure your CI/CD quality? Are there any metrics you are using for measuring the quality?
@@ -211,7 +211,7 @@ This situation might lead to bugs which hard to identify and reproduce.
-How to deal with configuration drift?
+How to deal with a configuration drift?
@@ -220,14 +220,6 @@ This situation might lead to bugs which hard to identify and reproduce.
Note: cross-dependency is when you have two or more changes to separate projects and you would like to test them in mutual build instead of testing each change separately.
-
-In what scenarios would you prefer to use SQL?
-
- * Homogeneous data, no changes anticipated
- * ACID compliance is important
-
-
-
## Jenkins
@@ -265,11 +257,11 @@ Note: cross-dependency is when you have two or more changes to separate projects
-What type of jobs are there? Which types have you used and why?
+What type of jobs are there? Which types have you used?
-How did you report build results to users? What ways are you familiar with?
+How did you report build results to users? What ways are you familiar with for reporting results?
@@ -295,10 +287,6 @@ Note: cross-dependency is when you have two or more changes to separate projects
There are four teams in your organization. How to prioritize the builds of each team? So the jobs of team x will always run before team y for example
-
-Do you have experience with developing a Jenkins plugin? Can you describe this experience?
-
-
If you are managing a dozen of jobs, you can probably use the Jenkins UI. How do you manage the creation and deletion of hundreds of jobs every week/month?
@@ -314,10 +302,17 @@ Note: cross-dependency is when you have two or more changes to separate projects
How would you implement an option of a starting a build from a certain stage and not from the beginning?
+##### Jenkins Dev
+
+
+Do you have experience with developing a Jenkins plugin? Can you describe this experience?
+
+
Have you written Jenkins scripts? If yes, what for and how they work?
+
## Cloud
@@ -328,7 +323,7 @@ Note: cross-dependency is when you have two or more changes to separate projects
-What types of Cloud Computing there are?
+What types of Cloud Computing are there?
IAAS
PAAS