Update docs to 4.0.0

Author: DanielJette

docs/docusaurus.config.js

@@ -37,7 +37,7 @@ const config = {
           lastVersion: 'current',
           versions: {
             current: {
-              label: '3.2.3',
+              label: '4.0.0',
             },
           },
           sidebarPath: require.resolve('./sidebars.js'),

docs/versioned_docs/version-3.2.3/get-started/6-verify-tests.md

@@ -23,7 +23,7 @@ $ ./gradlew app:screenshotTest
 
 ## Test failures
 
-By default, Testify will use a strict binary comparison. This means that any difference in the binary value used for any of the pixels will be considered a failure. You may wish to adjust the matching tolerance through the use of the `exactness` tolerance. A value of less than `1.0f` will result in a more leniant comparison which will exclude visually similar pixels. For more information on Testify's tolerance implementation, please read the blog post [_Accounting for platform differences_](../../blog/platform-differences).
+By default, Testify will use a strict binary comparison. This means that any difference in the binary value used for any of the pixels will be considered a failure. You may wish to adjust the matching tolerance through the use of the `exactness` tolerance. A value of less than `1.0f` will result in a more leniant comparison which will exclude visually similar pixels. For more information on Testify's tolerance implementation, please read the blog post [_Accounting for platform differences_](../../../blog/platform-differences).
 
 ### Tolerance
 

docs/versioned_docs/version-3.2.3/recipes/13-software-rendering.md

@@ -10,7 +10,7 @@ Please read more about [Hardware acceleration](https://developer.android.com/gui
 :::caution
 **Software rendering is not recommended.**
 
-The software rendering pipeline on Android does not produce the same results as the default hardware rendering and can omit shadows, elevation and other advanced features. If you're having difficulty with flaky or inconsistent rendering, it is recommended that you consider the options presented in [Accounting for platform differences](../../blog/platform-differences).
+The software rendering pipeline on Android does not produce the same results as the default hardware rendering and can omit shadows, elevation and other advanced features. If you're having difficulty with flaky or inconsistent rendering, it is recommended that you consider the options presented in [Accounting for platform differences](../../../blog/platform-differences).
 :::
 
 <Tabs>

docs/versioned_docs/version-3.2.3/recipes/17-custom-compare.md

@@ -22,7 +22,7 @@ typealias CompareMethod = (baselineBitmap: Bitmap, currentBitmap: Bitmap) -> Boo
 
 Before writing your own comparison method, consider that Testify provides multiple built-in mechanisms to customize the comparison of bitmaps. You can easily [_increase the matching tolerance_](tolerance) or [_exclude a region from the comparison_](exclude-regions).
 
-Please also see [_Accounting for platform differences_](../../blog/platform-differences) for more insight into handling unintended differences in your rendering.
+Please also see [_Accounting for platform differences_](../../../blog/platform-differences) for more insight into handling unintended differences in your rendering.
 
 :::
 

docs/versioned_docs/version-3.2.3/recipes/4-tolerance.md

@@ -11,7 +11,7 @@ By providing a value less than 1 to `exactness`, a test will be more tolerant to
 
 :::tip
 
-Please also see [_Accounting for platform differences_](../../blog/platform-differences) for more insight into handling unintended differences in your rendering.
+Please also see [_Accounting for platform differences_](../../../blog/platform-differences) for more insight into handling unintended differences in your rendering.
 
 :::