Skip to content

Commit 72e5e49

Browse files
committed
minor #7813 Update deployment.rst (timothymctim, javiereguiluz)
This PR was submitted for the 3.2 branch but it was merged into the 2.7 branch instead (closes #7813). Discussion ---------- Update deployment.rst Fix typos and style. Commits ------- 54e320f Minor reword 072370e Update deployment.rst
2 parents 4f23382 + 54e320f commit 72e5e49

File tree

1 file changed

+5
-5
lines changed

1 file changed

+5
-5
lines changed

deployment.rst

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -80,7 +80,7 @@ specifically tailored to the requirements of Symfony.
8080
`Capistrano`_ with `Symfony plugin`_
8181
`Capistrano`_ is a remote server automation and deployment tool written in Ruby.
8282
`Symfony plugin`_ is a plugin to ease Symfony related tasks, inspired by `Capifony`_
83-
(which works only with Capistrano 2 )
83+
(which works only with Capistrano 2).
8484

8585
`sf2debpkg`_
8686
Helps you build a native Debian package for your Symfony project.
@@ -181,12 +181,12 @@ setup:
181181
* Pushing assets to a CDN
182182
* ...
183183

184-
Application Lifecycle: Continuous Integration, QA, etc
185-
------------------------------------------------------
184+
Application Lifecycle: Continuous Integration, QA, etc.
185+
-------------------------------------------------------
186186

187187
While this entry covers the technical details of deploying, the full lifecycle
188-
of taking code from development up to production may have a lot more steps
189-
(think deploying to staging, QA (Quality Assurance), running tests, etc).
188+
of taking code from development up to production may have more steps:
189+
deploying to staging, QA (Quality Assurance), running tests, etc.
190190

191191
The use of staging, testing, QA, continuous integration, database migrations
192192
and the capability to roll back in case of failure are all strongly advised. There

0 commit comments

Comments
 (0)