[ieeeSW] Grammarly on Synchronocity section

Diego Araújo
1 parent 6e2e8e69
Showing 1 changed file with 4 additions and 4 deletions Show diff stats
ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
@@ -263,11 +263,11 @@ production environment for analysts’ validation.
 ### Synchronicity Between Government and Development
  
 Despite the positive impacts that the CD pipeline brought to the project, its
-implementation was not easy at first. The CD pipeline performance depended on
-the synchronicity between developers and government analysts, so that the
+implementation was not smooth at first. The CD pipeline performance depended on
+the synchronicity between developers and government analysts so that the
 latter were prepared to start a step as soon as the former concluded the
-previous step, and vice versa. Initially, this concern was not contemplated
-in the agenda of the governmental team, which generated delays in the validation
+previous step and vice versa. Initially, the agenda of the government team
+did not contemplate this concern, which generated delays in the validation
 of new features. This situation combined with governmental bureaucracy
 (up to 3 days) to release access to the production environment resulted in
 additional delays for the deployment step to begin. This problem was softened
...	...	@@ -263,11 +263,11 @@ production environment for analysts’ validation.
263	263	### Synchronicity Between Government and Development
264	264
265	265	Despite the positive impacts that the CD pipeline brought to the project, its
266		-implementation was not easy at first. The CD pipeline performance depended on
267		-the synchronicity between developers and government analysts, so that the
	266	+implementation was not smooth at first. The CD pipeline performance depended on
	267	+the synchronicity between developers and government analysts so that the
268	268	latter were prepared to start a step as soon as the former concluded the
269		-previous step, and vice versa. Initially, this concern was not contemplated
270		-in the agenda of the governmental team, which generated delays in the validation
	269	+previous step and vice versa. Initially, the agenda of the government team
	270	+did not contemplate this concern, which generated delays in the validation
271	271	of new features. This situation combined with governmental bureaucracy
272	272	(up to 3 days) to release access to the production environment resulted in
273	273	additional delays for the deployment step to begin. This problem was softened
...	...