Jan 26, 2021 · Jan 20, 2021 · Jan 20, 2021
diff --git a/_docs/administration/behind-the-firewall.md b/_docs/administration/behind-the-firewall.md
 this solution is very effective as far as security is concerned, it places a lot of overhead on the customer, as all updates
 and improvements done in the platform must also be transferred to the customer premises.

 The Hybrid approach places a Codefresh runner within customer premises while the UI (and management platform) stays in the Codefresh SaaS.
 This Hybrid approach places a Codefresh runner within customer premises while the UI (and management platform) stays in the Codefresh SaaS.

 Here is the overall architecture:

diff --git a/_docs/administration/codefresh-runner.md b/_docs/administration/codefresh-runner.md
 ```
 [Alternative install methods](https://codefresh-io.github.io/cli/installation/)

 Authenticate thecli
 Authenticate theCLI
 ```
 codefresh auth create-context --api-key {API_KEY}
 ```
Original file line number	Diff line number	Diff line change
Expand Up		@@ -17,7 +17,7 @@ Codefresh has an on-premise installation where the whole platform is installed o
		this solution is very effective as far as security is concerned, it places a lot of overhead on the customer, as all updates
		and improvements done in the platform must also be transferred to the customer premises.

		The Hybrid approach places a Codefresh runner within customer premises while the UI (and management platform) stays in the Codefresh SaaS.
		This Hybrid approach places a Codefresh runner within customer premises while the UI (and management platform) stays in the Codefresh SaaS.

		Here is the overall architecture:

Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -37,7 +37,7 @@ npm install -g codefresh
		```
		[Alternative install methods](https://codefresh-io.github.io/cli/installation/)

		Authenticate thecli
		Authenticate theCLI
		```
		codefresh auth create-context --api-key {API_KEY}
		```
Expand Down