cleanup links and pages (#7)

Author: hacdias

SUMMARY.md

@@ -7,7 +7,7 @@
   * [Synchronization service](concepts-and-architecture/sync-service.md)
   * [Networking](concepts-and-architecture/networking.md)
   * [Sidecar](concepts-and-architecture/sidecar.md)
-  * [Builders](concepts-and-architecture/builders-1.md)
+  * [Builders](concepts-and-architecture/builders.md)
   * [Runners](concepts-and-architecture/runners.md)
   * [Runtime environment \(runenv\)](concepts-and-architecture/runtime.md)
   * [Client-Server communication](concepts-and-architecture/client-server-communication.md)

concepts-and-architecture/README.md

@@ -18,7 +18,7 @@ To help you situate yourself, this architecture diagram provides a bird's-eye vi
 
 {% page-ref page="sidecar.md" %}
 
-{% page-ref page="builders-1.md" %}
+{% page-ref page="builders.md" %}
 
 {% page-ref page="runners.md" %}
 

concepts-and-architecture/builders-1.md renamed to concepts-and-architecture/builders.md

@@ -4,7 +4,7 @@ description: What are Testground runners?
 
 # Runners
 
-A **runner** is a component that takes _**build artifact**_ produced by a [Builder](builders-1.md), and schedules a test run of a test case within the test plan, on the Testground deployment, with the specified number of instances and test parameters.
+A **runner** is a component that takes _**build artifact**_ produced by a [Builder](builders.md), and schedules a test run of a test case within the test plan, on the Testground deployment, with the specified number of instances and test parameters.
 
 ```text
                                                           ☟

concepts-and-architecture/runners.md

@@ -24,7 +24,7 @@ runner = "local:exec"
 
 ### Builder and runner options
 
-The next few sections are options passed to each builder and runner when they are selected. Make sure to enable any [builders](../concepts-and-architecture/builders-1.md#supported-builders) and [runners](../concepts-and-architecture/runners.md#supported-runners) you want to use! The following section enables all runners and passes configurations. Of particular interest is the module path. Make sure this is correct to ensure code can be correctly imported.
+The next few sections are options passed to each builder and runner when they are selected. Make sure to enable any [builders](../concepts-and-architecture/builders.md#supported-builders) and [runners](../concepts-and-architecture/runners.md#supported-runners) you want to use! The following section enables all runners and passes configurations. Of particular interest is the module path. Make sure this is correct to ensure code can be correctly imported.
 
 ```yaml
 [builders."docker:go"]