Adjusted cnb specific documentation

Co-authored-by: Ralf Pannemans <[email protected]>

Author: 2 people

classical/binary/index.html.md.erb renamed to binary/index.html.md.erb

@@ -1,5 +1,5 @@
 ---
-title: Classical buildpacks
+title: Classic Buildpacks
 owner: Buildpacks
 ---
 
@@ -16,25 +16,25 @@ This limitation occurs when the deployment is behind a firewall, or when adminis
 
 The following topics discuss different usage scenarios for buildpacks in Cloud Foundry:
 
-* [How buildpacks work](understand-buildpacks.html)
+* [How buildpacks work](./understand-buildpacks.html)
 
-* [Stack association](stack-association.html)
+* [Stack association](./stack-association.html)
 
-* [Pushing an app with multiple buildpacks](use-multiple-buildpacks.html)
+* [Pushing an app with multiple buildpacks](./use-multiple-buildpacks.html)
 
-* [Using a proxy](proxy-usage.html)
+* [Using a proxy](./proxy-usage.html)
 
-* [Supported binary dependencies](supported-binary-dependencies.html)
+* [Supported binary dependencies](./supported-binary-dependencies.html)
 
-* [Production server configuration](prod-server.html)
+* [Production server configuration](./prod-server.html)
 
 ## <a id='system-buildpacks'></a> Cloud Foundry Buildpacks
 
-For information about the existing buildpacks that Cloud Foundry supports, see [CF Buildpack Languages and Sources](system-buildpacks.html).
+For information about the existing buildpacks that Cloud Foundry supports, see [CF Buildpack Languages and Sources](./system-buildpacks.html).
 
 ## <a id='sidecar-buildpacks'></a> Sidecar buildpacks
 
-For information about deploying a sidecar buildpack, see [Sidecar buildpack](sidecar-buildpacks.html).
+For information about deploying a sidecar buildpack, see [Sidecar buildpack](./sidecar-buildpacks.html).
 
 ## <a id='community-buildpacks'></a> Community buildpacks
 

classical/buildpack-ci-index.html.md.erb renamed to buildpack-ci-index.html.md.erb

@@ -19,8 +19,13 @@ You can use multiple buildpacks for your app
 
 For example:
 
+<p class="note">
+<span class="note__title"><strong>Note</strong></span>
+You must use cf CLI v9 or later.</p>
+
+
 ```
- <code>cf push APP-NAME --lifecycle cnb -b FIRST-BUILDPACK -b SECOND-BUILDPACK</code>
+ <code>cf push APP-NAME --lifecycle cnb -b docker://FIRST-BUILDPACK -b docker://SECOND-BUILDPACK</code>
 ```
 
 In this case <em>all</em> buildpacks must `detect` and `build` is called in the given order.

classical/index.html.md.erb renamed to classic.html.md.erb

@@ -8,7 +8,3 @@ topics are applicable to all supported buildpack languages:
 
 * [Working with buildpacks in Cloud Foundry](./understand-buildpacks.html).
 
-* [Stack association](../classical/stack-association.html).
-
-* [Pushing an app with multiple buildpacks](../classical/use-multiple-buildpacks.html).
-

cnb/understand-buildpacks.html.md.erb

@@ -1,11 +1,11 @@
 ---
-title: Cloud Foundry buildpacks
+title: Cloud Foundry Buildpacks
 owner: Buildpacks
 ---
 
 Buildpacks provide framework and runtime support for your apps. Buildpacks typically examine your apps to
 determine what dependencies to download and how to configure your apps to communicate with bound services.
 
 
-In Cloud Foundry, you can use 2 types of buildpacks. The [classical buildpacks](./classical/) (aka `v2`) and the
-[Cloud Native Buildpacks](./cnb/) (aka `v3`).
+In Cloud Foundry, you can use 2 types of buildpacks. [The Classic Buildpacks](./classic/) (aka `v2`) and the
+[Cloud Native Buildpacks](./cnb/) (aka `v3`).

cnb/using.html.md.erb

@@ -1,5 +1,5 @@
 ---
-title: Using classical buildpacks in Cloud Foundry
+title: Using Classic Buildpacks in Cloud Foundry
 owner: Buildpacks
 ---