updates

Author: vkryachko

contributor-docs/components/components.md

@@ -5,6 +5,8 @@ permalink: /components
 
 # Firebase Components
 
+{:toc}
+
 Firebase is known for being easy to use and requiring no/minimal configuration at runtime.
 Just adding SDKs to the app makes them discover each other to provide additional functionality,
 e.g. `Firestore` automatically integrates with `Auth` if present in the app.
@@ -127,7 +129,7 @@ At this point `FirebaseApp` will instantiate them and use the `ComponentRuntime`
 
 * **Component A depends on Component B** if `B` depends on an `interface` that `A` implements.
 * **For any Interface I, only one component is allowed to implement I**(with the exception of
-  [Multibindings]({{ site.baseurl }}{% link components/multibindings.md %})). If this invariant is violated, the container will
+  [Set Dependencies]({{ site.baseurl }}{% link components/dependencies.md %}#set-dependencies)). If this invariant is violated, the container will
   fail to start at runtime.
 * **There must not be any dependency cycles** among components. See Dependency Cycle Resolution on how this limitation can
   be mitigated

contributor-docs/components/dependencies.md

@@ -4,6 +4,8 @@ parent: Firebase Components
 
 # Dependencies
 
+{:toc}
+
 This page gives an overview of various different dependency types supported by the Components Framework.
 
 ## Background
@@ -142,9 +144,7 @@ See [Dynamic Module Support]({{ site.baseurl }}{% link components/dynamic_module
 
 ## Set Dependencies
 
-[Multibindings]({{ site.baseurl }}{% link components/multibindings.md %}) support in the Components Framework allows
-registering components to be part of a set, such components are registered explicitly to be a part of a `Set<T>`
-as opposed to be a unique value of `T`:
+The Components Framework allows registering components to be part of a set, such components are registered explicitly to be a part of a `Set<T>` as opposed to be a unique value of `T`:
 
 ```java
 // Sdk 1
@@ -185,5 +185,3 @@ Component.builder(MyClass.class)
     .factory(c -> MyClass(c.setOf(SomeType.class), c.setOfProvider(SomeOtherType.class)))
     .build();
 ```
-
-See [Multibindings]({{ site.baseurl }}{% link components/multibindings.md %}) for more details.

contributor-docs/components/executors.md

@@ -4,6 +4,8 @@ parent: Firebase Components
 
 # Executors
 
+{:toc}
+
 ## Intro
 
 OS threads are a limited resource that needs to be used with care. In order to minimize the number of threads used by Firebase

contributor-docs/components/multibindings.md

@@ -78,4 +78,4 @@ public class MyRegistrar implements ComponentRegistrar {
 
 This registrar is then registered in `AndroidManifest.xml` of the SDK and is used by `FirebaseApp` to discover all components and construct the dependency graph.
 
-More details in [Firebase Components]({{ site.baseurl }}{% link components/components.md %})).
+More details in [Firebase Components]({{ site.baseurl }}{% link components/components.md %}).