fix: lint

Author: mdelapenya

content/manuals/testcontainers/benefits.md

@@ -8,7 +8,7 @@ aliases:
 - /testcontainers/benefits/
 ---
 
-### Benefits of using Testcontainers:
+### Benefits of using Testcontainers
 
 * **On-demand isolated infrastructure provisioning:**
 You don't need to have a pre-provisioned integration testing infrastructure. 

content/manuals/testcontainers/getting-started/go.md

@@ -28,7 +28,7 @@ _Testcontainers for Go_ is tested against those two latest Go releases, therefor
 
 _Testcontainers for Go_ uses [go mod](https://blog.golang.org/using-go-modules) and you can get it installed via:
 
-```
+```bash
 go get github.com/testcontainers/testcontainers-go
 ```
 
@@ -93,7 +93,7 @@ automatically handles nil container so is safe to use even in the error case.
 
 > [!TIP]
 >
-> Look at [features/garbage_collector](/features/garbage_collector/) to know another
+> Look at [features/garbage_collector](https://golang.testcontainers.org/features/garbage_collector/) to know another
 > way to clean up resources.
 
 ## Step 3: Make your code talk to the container

content/manuals/testcontainers/getting-started/java.md

@@ -117,7 +117,7 @@ underTest = new RedisBackedCache(address, port);
 > not work on your current or future CI environment. As such, **avoid hard-coding** the address, and use 
 > `getHost()` instead.
 
-### Step 4: Run the tests!
+### Step 4: Run the tests
 
 That's it!
 
@@ -282,7 +282,7 @@ Those attributes can be helpful when:
 current environment. Set `disabledWithoutDocker` to `true`.
 * Enable parallel container initialization instead of sequential (by default). Set `parallel` to `true`.
 
-### Step 5: Run the tests!
+### Step 5: Run the tests
 
 That's it!
 
@@ -431,7 +431,7 @@ underTest = new RedisBackedCache(address, port)
 > not work on your current or future CI environment. As such, **avoid hard-coding** the address, and use 
 > `containerIpAddress` instead.
 
-### Step 4: Run the tests!
+### Step 4: Run the tests
 
 That's it!