fix tip 3

Author: azkrishpy

README.md

@@ -30,24 +30,24 @@ The AWS-C-S3 library is an asynchronous AWS S3 client focused on maximizing thro
    export AWS_CRT_S3_MEMORY_LIMIT_IN_GIB=4  # 4 GiB limit
    ```
 
-> [!TIP]
-   > You can also control memory limit *in bytes* using client config. The client config takes precedence over the environment variable (memory_limit_in_bytes needs to be set to a non-zero value).
-   > ```c
-   >    struct aws_s3_client_config config = {
-   >        .memory_limit_in_bytes = GB_TO_BYTES(4), // 4 GiB limit
-   >        // ... other configuration
-   >    };
-   > ```
-
    **Default Behavior**:
-   If neither is set (config is 0 and environment variable is not set), the client sets a default memory limit based on the target throughput.
+   When nothing is set, the client sets a default memory limit based on the target throughput.
 
    **Notes**:
    * The limit applies per client. If multiple clients created, limit will apply to each separately.
    * The environment variable value must be a valid positive integer representing gigabytes (GiB).
    * The value is converted from GiB to bytes internally (1 GiB = 1024³ bytes).
    * Invalid values or overflow conditions will cause client creation to fail with `AWS_ERROR_INVALID_ARGUMENT`.
 
+> [!TIP]
+> You can also control memory limit *in bytes* using client config. The client config takes precedence over the environment variable (memory_limit_in_bytes needs to be set to a non-zero value).
+> ```c
+>    struct aws_s3_client_config config = {
+>        .memory_limit_in_bytes = GB_TO_BYTES(4), // 4 GiB limit
+>        // ... other configuration
+>    };
+> ```
+
 2. **Maximum Parts Pending Read - `AWS_CRT_S3_MAX_PARTS_PENDING_READ`**
 
    Controls the maximum number of parts that can be pending read from the input stream during a multipart upload. Higher values may improve upload throughput for large files by allowing more parts to be read in parallel, at the cost of higher memory usage.