[i3eSW] Minor fixes

Melissa Wen
1 parent 4cf01cd1
Showing 1 changed file with 2 additions and 2 deletions Show diff stats
ieeeSW/releaseEng3/IEEE_ThemeIssue_ReleaseEng_CD.md
@@ -286,13 +286,13 @@ available to allocate for the building of the pipeline. The construction and
 maintenance of the CD process were possible by taking some decisions to mature
 the project:
-1. _Selecting the most experienced professionals and some developers of the
+1. _Select the most experienced professionals and some developers of the
 project to work on a specific team for DevOps._ These professionals used their
 experiences in OSS projects to get an initial proposal for the deployment process.
 The solution enabled us to automate the deployment, even though the process was
 still rudimentary.
-2. _Interchanging team members and encouraging teammates to migrate to DevOps
+2. _Interchange team members and encouraging teammates to migrate to DevOps
 team._ The benefits of these movements were twofold: mitigating the difficulty
 to pass the knowledge between DevOps developers and features developers, and
 evolving the process on-the-fly.
	@@ -286,13 +286,13 @@ available to allocate for the building of the pipeline. The construction and		@@ -286,13 +286,13 @@ available to allocate for the building of the pipeline. The construction and
286	maintenance of the CD process were possible by taking some decisions to mature	286	maintenance of the CD process were possible by taking some decisions to mature
287	the project:	287	the project:
288		288
289	-1. _Selecting the most experienced professionals and some developers of the	289	+1. _Select the most experienced professionals and some developers of the
290	project to work on a specific team for DevOps._ These professionals used their	290	project to work on a specific team for DevOps._ These professionals used their
291	experiences in OSS projects to get an initial proposal for the deployment process.	291	experiences in OSS projects to get an initial proposal for the deployment process.
292	The solution enabled us to automate the deployment, even though the process was	292	The solution enabled us to automate the deployment, even though the process was
293	still rudimentary.	293	still rudimentary.
294		294
295	-2. _Interchanging team members and encouraging teammates to migrate to DevOps	295	+2. _Interchange team members and encouraging teammates to migrate to DevOps
296	team._ The benefits of these movements were twofold: mitigating the difficulty	296	team._ The benefits of these movements were twofold: mitigating the difficulty
297	to pass the knowledge between DevOps developers and features developers, and	297	to pass the knowledge between DevOps developers and features developers, and
298	evolving the process on-the-fly.	298	evolving the process on-the-fly.