Mar 18, 2020 · Mar 17, 2020 · Mar 18, 2020
diff --git a/_docs/configure-ci-cd-pipeline/build-status.md b/_docs/configure-ci-cd-pipeline/build-status.md

 ## Finding the build badge of your project

 In the pipeline view of a project expand the *General settings*. Next to the *badges* section you will find a link to the build badge.
 In the pipeline view of a project, select the *Settings* tab and then click *General*. Next to the *badges* section you will find a link to the build badge.

 {% include
 image.html

 Click on it and you will get a new dialog where you can select

 * The branch that will be used for monitoring
 * The graphical style of the badge (two styles are offered)
 * The syntax for the badge

diff --git a/_docs/configure-ci-cd-pipeline/pipeline-caching.md b/_docs/configure-ci-cd-pipeline/pipeline-caching.md
 {: .table .table-bordered .table-hover}
 | Caching mechanism          | Activation              | Used in                   | Comments |
 | -------------- | ---------------------------- |-------------------------| -------------------------|
 | Distributed Docker step caching       | Automatic | All pipeline [steps]({{site.baseurl}}/docs/codefresh-yaml/steps/) | |
 | Distributed Docker step/image caching       | Automatic | All pipeline [steps]({{site.baseurl}}/docs/codefresh-yaml/steps/) | |
 | Distributed Docker layer caching  | Automatic |  Pipeline [build steps]({{site.baseurl}}/docs/codefresh-yaml/steps/build/) | Mimics local Docker layer cache|
 | Caching from previous built image  | Automatic |  Pipeline build steps | Distributed version of `--cache-from`|
 | Docker registry caching  | Automatic |  Pipeline build steps | Works only for the [integrated Docker registry]({{site.baseurl}}/docs/docker-registries/codefresh-registry/)|

 If you run this pipeline multiple times you will see multiple entries in the file `sample.txt`.

 >Note that if you run concurrent builds too quickly after one another, the Codefresh Volume will refresh [from scratch]({{site.baseurl}}/docs/configure-ci-cd-pipeline/pipeline-caching/#issues-with-parallel-builds-and-parallel-pipelines) instead of being cached between builds.

 {% include image.html
 lightbox="true"
 file="/images/pipeline/caching/codefresh-shared-volume.png"
 ## Codefresh cache size and eviction policy

 If you use the SAAS version of Codefresh, then you don't have any control of cache policies.
 The SAAS version is fully controlled by Codefresh personnel and the cache policies in place might clear cachesmoresooner than you think.
 The SAAS version is fully controlled by Codefresh personnel and the cache policies in place might clear caches sooner than you think.

 If you run a pipeline very infrequently it is possible to suffer many cache misses. If you also use obscure Docker images you might see them downloaded again and again.

diff --git a/_docs/configure-ci-cd-pipeline/shared-configuration.md b/_docs/configure-ci-cd-pipeline/shared-configuration.md
 max-width="50%"
 %}

 You can createtwo types of shared configuration:
 You can createfour types of shared configuration:

 * Shared Configuration/ Shared Secret
 * yaml/ secret yaml

 The shared configuration is for environment variables. The secret variant is the same thing but with encrypted values for sensitive data (such as access tokens).

 The shared yaml is for Helm value or any other generic information. The secret yaml encrypts the contents.
 * **Shared Configuration**: for environment variables
 * **Shared Secret**: for encrypted environment variables of sensitive data (access tokens, etc.)
 * **YAML**: for Helm values or any other generic information
 * **Secret YAML**: for above, but encrypts the contents

 You can create as many shared snippets as you want (with unique names).
Original file line number	Diff line number	Diff line change
Expand Up		@@ -30,7 +30,7 @@ Clicking the badge takes you into the build view of the pipeline.

		## Finding the build badge of your project

		In the pipeline view of a project expand the General settings. Next to the badges section you will find a link to the build badge.
		In the pipeline view of a project, select the Settings tab and then click General. Next to the badges section you will find a link to the build badge.

		{% include
		image.html
Expand All		@@ -44,7 +44,6 @@ max-width="50%"

		Click on it and you will get a new dialog where you can select

		* The branch that will be used for monitoring
		* The graphical style of the badge (two styles are offered)
		* The syntax for the badge

Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -15,7 +15,7 @@ Here is a quick overview of all types of caching used in a Codefresh pipeline:
		{: .table .table-bordered .table-hover}
		\| Caching mechanism \| Activation \| Used in \| Comments \|
		\| -------------- \| ---------------------------- \|-------------------------\| -------------------------\|
		\| Distributed Docker step caching \| Automatic \| All pipeline [steps]({{site.baseurl}}/docs/codefresh-yaml/steps/) \| \|
		\| Distributed Docker step/image caching \| Automatic \| All pipeline [steps]({{site.baseurl}}/docs/codefresh-yaml/steps/) \| \|
		\| Distributed Docker layer caching \| Automatic \| Pipeline [build steps]({{site.baseurl}}/docs/codefresh-yaml/steps/build/) \| Mimics local Docker layer cache\|
		\| Caching from previous built image \| Automatic \| Pipeline build steps \| Distributed version of `--cache-from`\|
		\| Docker registry caching \| Automatic \| Pipeline build steps \| Works only for the [integrated Docker registry]({{site.baseurl}}/docs/docker-registries/codefresh-registry/)\|
Expand DownExpand Up		@@ -218,6 +218,8 @@ steps:

		If you run this pipeline multiple times you will see multiple entries in the file `sample.txt`.

		>Note that if you run concurrent builds too quickly after one another, the Codefresh Volume will refresh [from scratch]({{site.baseurl}}/docs/configure-ci-cd-pipeline/pipeline-caching/#issues-with-parallel-builds-and-parallel-pipelines) instead of being cached between builds.

		{% include image.html
		lightbox="true"
		file="/images/pipeline/caching/codefresh-shared-volume.png"
Expand DownExpand Up		@@ -292,7 +294,7 @@ The diagram above shows the following sequence of events:
		## Codefresh cache size and eviction policy

		If you use the SAAS version of Codefresh, then you don't have any control of cache policies.
		The SAAS version is fully controlled by Codefresh personnel and the cache policies in place might clear cachesmoresooner than you think.
		The SAAS version is fully controlled by Codefresh personnel and the cache policies in place might clear caches sooner than you think.

		If you run a pipeline very infrequently it is possible to suffer many cache misses. If you also use obscure Docker images you might see them downloaded again and again.

Expand Down
Original file line number	Diff line number	Diff line change
Expand Up		@@ -31,14 +31,12 @@ caption="Creating shared configuration snippets"
		max-width="50%"
		%}

		You can createtwo types of shared configuration:
		You can createfour types of shared configuration:

		* Shared Configuration/ Shared Secret
		* yaml/ secret yaml

		The shared configuration is for environment variables. The secret variant is the same thing but with encrypted values for sensitive data (such as access tokens).

		The shared yaml is for Helm value or any other generic information. The secret yaml encrypts the contents.
		* Shared Configuration: for environment variables
		* Shared Secret: for encrypted environment variables of sensitive data (access tokens, etc.)
		* YAML: for Helm values or any other generic information
		* Secret YAML: for above, but encrypts the contents

		You can create as many shared snippets as you want (with unique names).

Expand Down