aggregate troubleshooting page into integration, remove duplicate protobuf

docs/docs/01-ibc/02-integration.md

@@ -218,13 +218,11 @@ var (
 )
 ```
 
-#### Integrating light clients
+### Integrating light clients
 
-> Note that from v9 onwards, all light clients are expected to implement the [`LightClientInterface` interface](../03-light-clients/01-developer-guide/02-light-client-module.md#implementing-the-lightclientmodule-interface) defined by core IBC, and have to be explicitly registered in a chain's app.go. This is in contrast to earlier versions of ibc-go when `07-tendermint` and `06-solomachine` were added out of the box. Follow the steps below to integrate the `07-tendermint` light client.
+> Note that from v7 onwards, all light clients are expected to implement the [`LightClientInterface` interface](../03-light-clients/01-developer-guide/02-light-client-module.md#implementing-the-lightclientmodule-interface) defined by core IBC, and have to be explicitly registered in a chain's app.go. This is in contrast to earlier versions of ibc-go when `07-tendermint` and `06-solomachine` were added out of the box. Follow the steps below to integrate the `07-tendermint` light client.
 
-All light clients must be registered with `module.Manager` in a chain's app.go file.
-
-The following code example shows how to instantiate `07-tendermint` light client module and register its `ibctm.AppModule`.
+All light clients must be registered with `module.Manager` in a chain's app.go file. The following code example shows how to instantiate `07-tendermint` light client module and register its `ibctm.AppModule`.
 
 ```go title="app.go"
 import (
@@ -253,6 +251,16 @@ app.ModuleManager = module.NewManager(
 )
 ```
 
+#### Allowed Clients Params
+
+The allowed clients parameter defines an allow list of client types supported by the chain. The 
+default value is a single-element list containing the [`AllowedClients`](https://github.com/cosmos/ibc-go/blob/main/modules/core/02-client/types/client.pb.go#L248-L253) wildcard (`"*"`). Alternatively, the parameter
+may be set with a list of client types (e.g. `"06-solomachine","07-tendermint","09-localhost"`).
+A client type that is not registered on this list will fail upon creation or on genesis validation.
+Note that, since the client type is an arbitrary string, chains must not register two light clients
+which return the same value for the `ClientType()` function, otherwise the allow list check can be
+bypassed.
+
 ### Application ABCI ordering
 
 One addition from IBC is the concept of `HistoricalInfo` which is stored in the Cosmos SDK `x/staking` module. The number of records stored by `x/staking` is controlled by the `HistoricalEntries` parameter which stores `HistoricalInfo` on a per-height basis.

docs/docs/01-ibc/06-proposals.md

@@ -1,7 +1,7 @@
 ---
 title: Governance Proposals
 sidebar_label: Governance Proposals
-sidebar_position: 7
+sidebar_position: 6
 slug: /ibc/proposals
 ---
 

docs/docs/01-ibc/07-relayer.md

@@ -1,7 +1,7 @@
 ---
 title: Relayer
 sidebar_label: Relayer
-sidebar_position: 8
+sidebar_position: 7
 slug: /ibc/relayer
 ---
 

docs/docs/01-ibc/11-best-practices.md → docs/docs/01-ibc/08-best-practices.md

@@ -1,7 +1,7 @@
 ---
 title: Best Practices
 sidebar_label: Best Practices
-sidebar_position: 13
+sidebar_position: 8
 slug: /ibc/best-practices
 ---
 

docs/docs/01-ibc/12-permissioning.md → docs/docs/01-ibc/09-permissioning.md

@@ -1,7 +1,7 @@
 ---
 title: Permissioning
 sidebar_label: Permissioning
-sidebar_position: 14
+sidebar_position: 9
 slug: /ibc/permissioning
 ---