diff --git a/ee/ucp/deploy-application-package.md b/ee/ucp/deploy-application-package.md
index 4027f9f522..ddcdeed4da 100644
--- a/ee/ucp/deploy-application-package.md
+++ b/ee/ucp/deploy-application-package.md
@@ -8,11 +8,13 @@ keywords: ucp, swarm, kubernetes, application
 >
 > This is beta content. It is not yet complete and should be considered a work in progress. This content is subject to change without notice.
 
+## Application packages
+
 In Docker 2.1 EE, an application package has one of these formats:
 
 - **Three-file format**: Defined by a metadata.yml, a docker-compose.yml, and a settings.yml files inside a `my-app.dockerapp` folder. This is also called the folder format.
 - **Single-file format**: Defined by a data from the previously three files concatenated in the order givem and separated by `---\n` in a single file named named 'my-app.dockerapp'.
-- **Image forma   t**: Defined by a Docker image in the engine store or exported as a tarball.
+- **Image format**: Defined by a Docker image in the engine store or exported as a tarball.
 
 The docker-app binary lets a user render an application package to a Compose file using the settings values in the settings file or those specified by the user. This Compose file can then be deployed to a cluster running in Swarm mode or Kubernetes using `docker stack deploy` or to a single engine or Swarm classic cluster using `docker-compose up`.