diff --git a/jetty/content.md b/jetty/content.md
index be918c624..b0d89e501 100644
--- a/jetty/content.md
+++ b/jetty/content.md
@@ -8,19 +8,21 @@ Jetty is a pure Java-based HTTP (Web) server and Java Servlet container. While W
 
 # How to use this image.
 
-Run the default Jetty server:
+To run the default Jetty server in the background, use the following command:
 
 ```console
-$ docker run -d %%REPO%%:9
+$ docker run -d %%REPO%%
 ```
 
-You can test it by visiting `http://container-ip:8080` in a browser or, if you need access outside the host, on port 8888:
+You can test it by visiting `http://container-ip:8080` or `https://container-ip:8443/` in a browser. To expose your Jetty server to outside requests, use a port mapping as follows:
 
 ```console
-$ docker run -d -p 8888:8080 %%REPO%%:9
+$ docker run -d -p 80:8080 -p 443:8443 %%REPO%%
 ```
 
-You can then go to `http://localhost:8888` or `http://host-ip:8888` in a browser.
+This will map port 8080 inside the container as port 80 on the host and container port 8443 as host port 443. You can then go to `http://host-ip` or `https://host-ip` in a browser.
+
+## Environment
 
 The default Jetty environment in the image is:
 
@@ -39,19 +41,19 @@ For older EOL'd images based on Jetty 7 or Jetty 8, please follow the [legacy in
 The configuration of the Jetty server can be reported by running with the `--list-config` option:
 
 ```console
-$ docker run -d %%REPO%%:9 --list-config
+$ docker run -d %%REPO%% --list-config
 ```
 
 Configuration such as parameters and additional modules may also be passed in via the command line. For example:
 
 ```console
-$ docker run -d %%REPO%%:9 --modules=jmx jetty.threadPool.maxThreads=500
+$ docker run -d %%REPO%% --modules=jmx jetty.threadPool.maxThreads=500
 ```
 
 To update the server configuration in a derived Docker image, the `Dockerfile` may enable additional modules with `RUN` commands like:
 
 ```Dockerfile
-FROM jetty:9
+FROM jetty
 
 RUN java -jar "$JETTY_HOME/start.jar" --add-to-startd=jmx,stats
 ```
@@ -63,11 +65,25 @@ Modules may be configured in a `Dockerfile` by editing the properties in the cor
 To run `%%REPO%%` as a read-only container, have Docker create the `/tmp/jetty` and `/run/jetty` directories as volumes:
 
 ```console
-$ docker run -d --read-only -v /tmp/jetty -v /run/jetty %%REPO%%:9
+$ docker run -d --read-only -v /tmp/jetty -v /run/jetty %%REPO%%
 ```
 
 Since the container is read-only, you'll need to either mount in your webapps directory with `-v /path/to/my/webapps:/var/lib/jetty/webapps` or by populating `/var/lib/jetty/webapps` in a derived image.
 
+## HTTP/2 Support
+
+Starting with version 9.3, Jetty comes with built-in support for HTTP/2. However, due to potential license compatiblity issues with the ALPN library used to implement HTTP/2, the module is not enabled by default. In order to enable HTTP/2 support in a derived `Dockerfile` for private use, you can add a `RUN` command that enables the `http2` module and approve its license as follows:
+
+```Dockerfile
+FROM jetty
+
+RUN java -jar \$JETTY_HOME/start.jar --add-to-startd=http2 --approve-all-licenses
+```
+
+This will add an `http2.ini` file to the `$JETTY_BASE/start.d` directory and download the required ALPN libraries into `$JETTY_BASE/lib/alpn`, allowing the use of HTTP/2. HTTP/2 connections should be made via the same port as normal HTTPS connections (container port 8443). If you would like to enable the `http2` module via `$JETTY_BASE/start.ini` instead, substitute `--add-to-start` in place of `--add-to-startd` in the `RUN` command above.
+
+Once OpenJDK 9 becomes generally available with built-in support for ALPN, this image will be updated to enable HTTP/2 support by default.
+
 # Security
 
 By default, this image starts as user `root` and uses Jetty's `setuid` module to drop privileges to user `jetty` after initialization. The `JETTY_BASE` directory at `/var/lib/jetty` is owned by `jetty:jetty` (uid 999, gid 999).
@@ -75,5 +91,5 @@ By default, this image starts as user `root` and uses Jetty's `setuid` module to
 If you would like the image to start immediately as user `jetty` instead of starting as `root`, you can start the container with `-u jetty`:
 
 ```console
-$ docker run -d -u jetty %%REPO%%:9
+$ docker run -d -u jetty %%REPO%%
 ```