update docusaurus

Author: mkosir

website/src/pages/index.mdx

@@ -135,19 +135,6 @@ const removeFirstUser = (users: ReadonlyArray<User>) => {
 };
 ```
 
-### Return Types
-
-Including return type annotations is highly encouraged, although not required ([eslint rule](https://typescript-eslint.io/rules/explicit-function-return-type/)).
-
-Consider benefits when explicitly typing the return value of a function:
-
-- Return values makes it clear and easy to understand to any calling code what type is returned.
-- In the case where there is no return value, the calling code doesn't try to use the undefined value when it shouldn't.
-- Surface potential type errors faster in the future if there are code changes that change the return type of the function.
-- Easier to refactor, since it ensures that the return value is assigned to a variable of the correct type.
-- Similar to writing tests before implementation (TDD), defining function arguments and return type, gives you the opportunity to discuss the feature functionality and its interface ahead of implementation.
-- Although type inference is very convenient, adding return types can save TypeScript compiler a lot of work.
-
 ### Discriminated union
 
 If there's only one TypeScript feature to choose from, embrace discriminated unions.
@@ -186,6 +173,19 @@ Discriminated unions advantages:
 - Discriminated unions make refactoring and maintenance easier by providing a centralized definition of related types. When adding or modifying types within the union, the compiler reports any inconsistencies throughout the codebase.
 - IDEs can leverage discriminated unions to provide better autocompletion and type inference.
 
+### Return Types
+
+Including return type annotations is highly encouraged, although not required ([eslint rule](https://typescript-eslint.io/rules/explicit-function-return-type/)).
+
+Consider benefits when explicitly typing the return value of a function:
+
+- Return values makes it clear and easy to understand to any calling code what type is returned.
+- In the case where there is no return value, the calling code doesn't try to use the undefined value when it shouldn't.
+- Surface potential type errors faster in the future if there are code changes that change the return type of the function.
+- Easier to refactor, since it ensures that the return value is assigned to a variable of the correct type.
+- Similar to writing tests before implementation (TDD), defining function arguments and return type, gives you the opportunity to discuss the feature functionality and its interface ahead of implementation.
+- Although type inference is very convenient, adding return types can save TypeScript compiler a lot of work.
+
 ### Template Literal Types
 
 Embrace using template literal types, instead of just (wide) `string` type.