Merge branch 'master' of softwarepublico.gov.br:softwarepublico/articles

Paulo Meireles
2 parents 82ca6dc3 3e1dda9c
Showing 1 changed file with 9 additions and 5 deletions Show diff stats
ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
@@ -176,19 +176,23 @@ to use by our subsequent deployment scripts.
 The Validation Environment (VE) is a replica of the Production Environment
 (PE), with two exceptions: only the government officers and us had access to it
 and all the data is anonymised. To configure the environment, we use a
-configuration management tool. That maintained environment consistency which
-makes the deployment process simpler. Additionally, the packages we built on
+configuration management tool. That maintained environment consistency 
+simplifying the deployment process. Additionally, the packages we built on
 the last step were readily available to use by the management tool.
  
 The VE was used by the government agents to validate new features and required
 changes. Also, the VE was useful to verify the integrity of the entire portal
-as part of the next step in the pipeline.  Acceptance Tests
+as part of the next step in the pipeline.
+
+### Acceptance Tests
  
 After we completely deploy a new SPB Portal version in the VE, the government agents
 are responsible for checking features and/or bug fixes required by them. If the
-technicians identify a problem, they notify the developers, the problems are
+technicians identify a problem, they notify the developers. These problems are
 fixed and the pipeline restarts from scratch. If everything is validated, we
-move to production deployment.  Production Deployment
+move forward.
+
+### Production Deployment
  
 After the government authorizes the VE, we can finally begin the production
 deployment. We use the same configuration management tool with the same
...	...	@@ -176,19 +176,23 @@ to use by our subsequent deployment scripts.
176	176	The Validation Environment (VE) is a replica of the Production Environment
177	177	(PE), with two exceptions: only the government officers and us had access to it
178	178	and all the data is anonymised. To configure the environment, we use a
179		-configuration management tool. That maintained environment consistency which
180		-makes the deployment process simpler. Additionally, the packages we built on
	179	+configuration management tool. That maintained environment consistency
	180	+simplifying the deployment process. Additionally, the packages we built on
181	181	the last step were readily available to use by the management tool.
182	182
183	183	The VE was used by the government agents to validate new features and required
184	184	changes. Also, the VE was useful to verify the integrity of the entire portal
185		-as part of the next step in the pipeline. Acceptance Tests
	185	+as part of the next step in the pipeline.
	186	+
	187	+### Acceptance Tests
186	188
187	189	After we completely deploy a new SPB Portal version in the VE, the government agents
188	190	are responsible for checking features and/or bug fixes required by them. If the
189		-technicians identify a problem, they notify the developers, the problems are
	191	+technicians identify a problem, they notify the developers. These problems are
190	192	fixed and the pipeline restarts from scratch. If everything is validated, we
191		-move to production deployment. Production Deployment
	193	+move forward.
	194	+
	195	+### Production Deployment
192	196
193	197	After the government authorizes the VE, we can finally begin the production
194	198	deployment. We use the same configuration management tool with the same
...	...