Merge pull request #122 from samdulam/upgrade-docs

Note for ports 9000 and 8000

docs/v2.0-be/deploy/beinstalldocker.md

@@ -3,12 +3,11 @@ hide: toc
 ---
 
 # :fontawesome-brands-docker: Deploying Portainer Business in Docker
-
 Portainer is comprised of two elements, the Portainer Server, and the Portainer Agent. Both elements run as lightweight Docker containers on a Docker engine or within a Swarm cluster. Due to the nature of Docker, there are many possible deployment scenarios, however, we have detailed the most common below. Please use the scenario that matches your configuration.
 
 Note that the recommended deployment mode when using Swarm is using the Portainer Agent.
 
-By default, Portainer will expose the UI over the port 9000 and expose a TCP tunnel server over the port 8000. The latter is optional and is only required if you plan to use the Edge compute features with Edge agents.
+By default, Portainer will expose the UI over the port `#!Ruby 9000` and expose a TCP tunnel server over the port `#!Ruby 8000`. The latter is optional and is only required if you plan to use the Edge compute features with Edge agents.
 
 To see the requirements, please, visit the page of [requirements](/v2.0-be/deploy/requirements/).
 

docs/v2.0-be/deploy/beinstallk8s.md

@@ -3,8 +3,11 @@ hide: toc
 ---
 
 # :material-kubernetes: Deploying Portainer Business in Kubernetes
+Portainer is comprised of two elements, the Portainer Server, and the Portainer Agent. Both elements run as lightweight Docker containers on a Docker engine. There are many possible deployment scenarios, however, we have detailed the most common below. Please use the scenario that matches your configuration.
 
 
+By default, Portainer will expose the UI over the port `#!Ruby 9000` and expose a TCP tunnel server over the port `#!Ruby 8000`. The latter is optional and is only required if you plan to use the Edge compute features with Edge agents.
+
 
 To see the requirements, please, visit the page of [requirements](/v2.0-be/deploy/requirements/).
 

docs/v2.0-be/deploy/beinstallswarm.md

@@ -3,12 +3,11 @@ hide: toc
 ---
 
 # :fontawesome-brands-docker: Deploying Portainer Business in Docker Swarm
-
 Portainer is comprised of two elements, the Portainer Server, and the Portainer Agent. Both elements run as lightweight Docker containers on a Docker engine or within a Swarm cluster. Due to the nature of Docker, there are many possible deployment scenarios, however, we have detailed the most common below. Please use the scenario that matches your configuration.
 
 Note that the recommended deployment mode when using Swarm is using the Portainer Agent.
 
-By default, Portainer will expose the UI over the port 9000 and expose a TCP tunnel server over the port 8000. The latter is optional and is only required if you plan to use the Edge compute features with Edge agents.
+By default, Portainer will expose the UI over the port `#!Ruby 9000` and expose a TCP tunnel server over the port `#!Ruby 8000`. The latter is optional and is only required if you plan to use the Edge compute features with Edge agents.
 
 To see the requirements, please, visit the page of [requirements](/v2.0-be/deploy/requirements/).
 

docs/v2.0-be/deploy/requirements.md

@@ -1,4 +1,8 @@
 # Requirements
+Portainer is comprised of two elements, the Portainer Server, and the Portainer Agent. Both elements run as lightweight Docker containers on a Docker engine.
+
+By default, Portainer will expose the UI over the port `#!Ruby 9000` and expose a TCP tunnel server over the port `#!Ruby 8000`. The latter is optional and is only required if you plan to use the Edge compute features with Edge agents.
+
 
 Every single release of Portainer goes through an extensive testing process (functional tests, release tests, post release tests) to ensure that what we are creating actually works as expected. Obviously though, we cannot possibly test Portainer against every single configuration variant out there, so we have elected to test against just a subset.
 

docs/v2.0/deploy/ceinstalldocker.md

@@ -4,12 +4,11 @@ hide:
 ---
 
 # :fontawesome-brands-docker: Deploying Portainer CE in Docker
-
 Portainer is comprised of two elements, the Portainer Server, and the Portainer Agent. Both elements run as lightweight Docker containers on a Docker engine or within a Swarm cluster. Due to the nature of Docker, there are many possible deployment scenarios, however, we have detailed the most common below. Please use the scenario that matches your configuration.
 
 Note that the recommended deployment mode when using Swarm is using the Portainer Agent.
 
-By default, Portainer will expose the UI over the port 9000 and expose a TCP tunnel server over the port 8000. The latter is optional and is only required if you plan to use the Edge compute features with Edge agents.
+By default, Portainer will expose the UI over the port `#!Ruby 9000` and expose a TCP tunnel server over the port `#!Ruby 8000`. The latter is optional and is only required if you plan to use the Edge compute features with Edge agents.
 
 To see the requirements, please, visit the page of [requirements](/v2.0/deploy/requirements).
 

docs/v2.0/deploy/ceinstallk8s.md

@@ -3,8 +3,11 @@ hide: toc
 ---
 
 # :material-kubernetes: Deploying Portainer CE in Kubernetes
+Portainer is comprised of two elements, the Portainer Server, and the Portainer Agent. Both elements run as lightweight Docker containers on a Docker engine. There are many possible deployment scenarios, however, we have detailed the most common below. Please use the scenario that matches your configuration.
 
 
+By default, Portainer will expose the UI over the port `#!Ruby 9000` and expose a TCP tunnel server over the port `#!Ruby 8000`. The latter is optional and is only required if you plan to use the Edge compute features with Edge agents.
+
 
 To see the requirements, please, visit the page of [requirements](/v2.0/deploy/requirements).
 

docs/v2.0/deploy/ceinstallswarm.md

@@ -3,12 +3,11 @@ hide: toc
 ---
 
 # :fontawesome-brands-docker: Deploying Portainer CE in Docker Swarm
-
 Portainer is comprised of two elements, the Portainer Server, and the Portainer Agent. Both elements run as lightweight Docker containers on a Docker engine or within a Swarm cluster. Due to the nature of Docker, there are many possible deployment scenarios, however, we have detailed the most common below. Please use the scenario that matches your configuration.
 
 Note that the recommended deployment mode when using Swarm is using the Portainer Agent.
 
-By default, Portainer will expose the UI over the port 9000 and expose a TCP tunnel server over the port 8000. The latter is optional and is only required if you plan to use the Edge compute features with Edge agents.
+By default, Portainer will expose the UI over the port `#!Ruby 9000` and expose a TCP tunnel server over the port `#!Ruby 8000`. The latter is optional and is only required if you plan to use the Edge compute features with Edge agents.
 
 To see the requirements, please, visit the page of [requirements](/v2.0/deploy/requirements).
 

docs/v2.0/deploy/requirements.md

@@ -1,4 +1,8 @@
 # Requirements
+Portainer is comprised of two elements, the Portainer Server, and the Portainer Agent. Both elements run as lightweight Docker containers on a Docker engine.
+
+
+By default, Portainer will expose the UI over the port `#!Ruby 9000` and expose a TCP tunnel server over the port `#!Ruby 8000`. The latter is optional and is only required if you plan to use the Edge compute features with Edge agents.
 
 Every single release of Portainer goes through an extensive testing process (functional tests, release tests, post release tests) to ensure that what we are creating actually works as expected. Obviously though, we cannot possibly test Portainer against every single configuration variant out there, so we have elected to test against just a subset.
 

mkdocs.yml

@@ -301,6 +301,7 @@ markdown_extensions:
   - pymdownx.tabbed
   - pymdownx.superfences
   - pymdownx.details
+  - pymdownx.inlinehilite
   - fontawesome_markdown
   - meta
   - pymdownx.emoji: