Update modules/ROOT/partials/docker/image-proxy-service/image-proxy-service-installation.adoc

soritaheng · kemister85 · web-flow · commit e5e44e2a2bb5 · 2025-03-17T14:07:15.000+10:00
Co-authored-by: Karl Kemister-Sheppard &lt;karlkemistersheppard@gmail.com&gt;
diff --git a/modules/ROOT/partials/docker/image-proxy-service/image-proxy-service-installation.adoc b/modules/ROOT/partials/docker/image-proxy-service/image-proxy-service-installation.adoc
@@ -174,7 +174,7 @@ image-proxy-tiny-1  | 2025-01-08 15:02:37 [io-compute-1] INFO  o.h.blaze.server.
 . Test the service via cURL command
 
 +
-To verify that the Image Proxy service is set up and functioning correctly within the container, ensure the service is running on port 19040. Once active, it should be ready to receive requests. The expected outputs below confirm proper configuration, assuming http://good.com is in the allowed origins and http://bad.com is not.
+To verify that the Image Proxy service is set up and functioning correctly within the container, ensure the service is running on port `19040`. Once active, it should be ready to receive requests. The expected outputs below confirm proper configuration, assuming `http://good.com` is in the allowed origins and `http://bad.com` is not.
 
 +
 To check the service is running use:

Original file line number	Diff line number	Diff line change
`@@ -174,7 +174,7 @@ image-proxy-tiny-1 \| 2025-01-08 15:02:37 [io-compute-1] INFO o.h.blaze.server.`
`174`	`174`	`. Test the service via cURL command`
`175`	`175`
`176`	`176`	`+`
`177`		`-To verify that the Image Proxy service is set up and functioning correctly within the container, ensure the service is running on port 19040. Once active, it should be ready to receive requests. The expected outputs below confirm proper configuration, assuming http://good.com is in the allowed origins and http://bad.com is not.`
	`177`	+To verify that the Image Proxy service is set up and functioning correctly within the container, ensure the service is running on port `19040`. Once active, it should be ready to receive requests. The expected outputs below confirm proper configuration, assuming `http://good.com` is in the allowed origins and `http://bad.com` is not.
`178`	`178`
`179`	`179`	`+`
`180`	`180`	`To check the service is running use:`