use sembr, remove javadoc links, minor changes

Author: etrandafir93

docs/modules/docker_compose.md

@@ -4,13 +4,16 @@
 
 Similar to generic container support, it's also possible to run a bespoke set of services specified in a `docker-compose.yml` file. 
 
-This is especially useful for projects where Docker Compose  is already used in development or other environments to define services that an application may be dependent upon.
+This is especially useful for projects where Docker Compose is already used in development 
+or other environments to define services that an application may be dependent upon.
 
-The [`ComposeContainer`](http://static.javadoc.io/org.testcontainers/testcontainers/{{ latest_version }}/org/testcontainers/containers/ComposeContainer.html) leverages [Compose V2](https://www.docker.com/blog/announcing-compose-v2-general-availability/), making it easy to use the same dependencies from the development environment within tests.
+The `ComposeContainer` leverages [Compose V2](https://www.docker.com/blog/announcing-compose-v2-general-availability/),
+making it easy to use the same dependencies from the development environment within tests.
 
 ## Example
 
-A single class `ComposeContainer`, defined based on a `docker-compose.yml` file, should be sufficient to launch any number of services required by our tests:
+A single class `ComposeContainer`, defined based on a `docker-compose.yml` file, 
+should be sufficient to launch any number of services required by our tests:
 
 <!--codeinclude-->
 [Create a ComposeContainer](../../core/src/test/java/org/testcontainers/junit/ComposeContainerTest.java) inside_block:composeContainerConstructor
@@ -28,15 +31,17 @@ services:
     image: mysql:8.0.36
 ```
 
-Note that it is not necessary to define ports to be exposed in the YAML file, as this would inhibit the reuse/inclusion of the file in other contexts.
+Note that it is not necessary to define ports to be exposed in the YAML file, 
+as this would inhibit the reuse/inclusion of the file in other contexts.
 
-Instead, Testcontainers will spin up a small 'ambassador' container, which will proxy between the Compose-managed containers and ports that are accessible to our tests. This is done using a separate, minimal container that runs socat as a TCP proxy.
+Instead, Testcontainers will spin up a small 'ambassador' container, 
+which will proxy between the Compose-managed containers and ports that are accessible to our tests. 
 
 ## ComposeContainer vs DockerComposeContainer 
 
-So far, we discussed [`ComposeContainer`](http://static.javadoc.io/org.testcontainers/testcontainers/{{ latest_version }}/org/testcontainers/containers/ComposeContainer.html), which is the equivalent of docker compose [version 2](https://www.docker.com/blog/announcing-compose-v2-general-availability/). 
+So far, we discussed `ComposeContainer`, which is the equivalent of docker compose [version 2](https://www.docker.com/blog/announcing-compose-v2-general-availability/). 
 
-On the other hand, [`DockerComposeContainer`](http://static.javadoc.io/org.testcontainers/testcontainers/{{ latest_version }}/org/testcontainers/containers/DockerComposeContainer.html) utilizes Compose V1, which has been marked deprecated by Docker.
+On the other hand, `DockerComposeContainer` utilizes Compose V1, which has been marked deprecated by Docker.
 
 The two APIs are quite similar, and most examples provided on this page can be applied to both of them.
 
@@ -56,10 +61,13 @@ Let's use this API to create the URL that will enable our tests to access the Re
 
 ## Wait Strategies and Startup Timeouts
 Ordinarily Testcontainers will wait for up to 60 seconds for each exposed container's first mapped network port to start listening.
-
 This simple measure provides a basic check whether a container is ready for use.
 
-There are overloaded `withExposedService` methods that take a [`WaitStrategy`](http://static.javadoc.io/org.testcontainers/testcontainers/{{ latest_version }}/org/testcontainers/containers/wait/strategy/WaitStrategy.html) where we can specify a timeout strategy per container. We can either use the fluent API to crate a custom strategy or use one of the already existing ones, accessible via the static factory methods from of the [`Wait`](http://static.javadoc.io/org.testcontainers/testcontainers/{{ latest_version }}/org/testcontainers/containers/wait/strategy/Wait.html) class. 
+There are overloaded `withExposedService` methods that take a `WaitStrategy` 
+where we can specify a timeout strategy per container. 
+
+We can either use the fluent API to crate a [custom strategy](../features/startup_and_waits.md) or use one of the already existing ones, 
+accessible via the static factory methods from of the `Wait` class.
 
 For instance, we can wait for exposed port and set a custom timeout:
 <!--codeinclude-->
@@ -68,7 +76,8 @@ For instance, we can wait for exposed port and set a custom timeout:
 
 Needless to say, we can define different strategies for each service in our Docker Compose setup. 
 
-For example, our Redis container can wait for a successful redis-cli command, while our db service waits for a specific log message:
+For example, our Redis container can wait for a successful redis-cli command, 
+while our db service waits for a specific log message:
 
 <!--codeinclude-->
 [Wait for a custom command and a log message](../../core/src/test/java/org/testcontainers/junit/ComposeContainerWithWaitStrategies.java) inside_block:composeContainerWithCombinedWaitStrategies
@@ -82,7 +91,8 @@ For example, our Redis container can wait for a successful redis-cli command, wh
 
 We can override Testcontainers' default behaviour and make it use a `docker-compose` binary installed on the local machine. 
 
-This will generally yield an experience that is closer to running _docker compose_ locally, with the caveat that Docker Compose needs to be present on dev and CI machines.
+This will generally yield an experience that is closer to running _docker compose_ locally, 
+with the caveat that Docker Compose needs to be present on dev and CI machines.
 
 <!--codeinclude-->
 [Use ComposeContainer in 'Local Compose' mode](../../core/src/test/java/org/testcontainers/containers/ComposeProfilesOptionTest.java) inside_block:composeContainerWithLocalCompose
@@ -99,16 +109,16 @@ We can select what files should be copied only via `withCopyFilesInContainer`:
 In this example, only docker compose and env files are copied over into the container that will run the Docker Compose file.  
 By default, all files in the same directory as the compose file are copied over.
 
-We can use file and directory references. They are always resolved relative to the directory where the compose file resides.
-
-This can be used with [`DockerComposeContainer`](http://static.javadoc.io/org.testcontainers/testcontainers/{{ latest_version }}/org/testcontainers/containers/DockerComposeContainer.html) and [`ComposeContainer`](http://static.javadoc.io/org.testcontainers/testcontainers/{{ latest_version }}/org/testcontainers/containers/ComposeContainer.html).
+We can use file and directory references. 
+They are always resolved relative to the directory where the compose file resides.
 
 !!! note
 
-    This can be used with [`DockerComposeContainer`](http://static.javadoc.io/org.testcontainers/testcontainers/{{ latest_version }}/org/testcontainers/containers/DockerComposeContainer.html) and [`ComposeContainer`](http://static.javadoc.io/org.testcontainers/testcontainers/{{ latest_version }}/org/testcontainers/containers/ComposeContainer.html) - but **only in the containerized Compose (not with `Local Compose` mode)**.
+    This can be used with `DockerComposeContainer` and `ComposeContainer`, but **only in the containerized Compose (not with `Local Compose` mode)**.
 
 ## Using private repositories in Docker compose
-When Docker Compose is used in container mode (not local), it's needs to be made aware of Docker settings for private repositories. 
+When Docker Compose is used in container mode (not local), 
+it needs to be made aware of Docker settings for private repositories. 
 By default, those setting are located in `$HOME/.docker/config.json`. 
 
 There are 3 ways to specify location of the `config.json` for Docker Compose: