Update native directory path

docs/graalvm-compatibility-in-ballerina-libraries.md

@@ -206,9 +206,9 @@ This is not straightforward since Ballerina tests are not executed by a single U
 
 If the library requires any additional configurations that are generated by the tracing agent, then review the configurations and filter the required ones. The filtered configurations should be packed with the module to make it GraalVM compatible.
 
-1. If you have a `native` directory that holds the Java native code, then you can pack this configuration files in the `resources/META_INF/native-image/<group-id>/<artifact-id>/` directory.
+1. If you have a `native` directory that holds the Java native code, then you can pack this configuration files in the `src/main/resources/META-INF/native-image/<group-id>/<artifact-id>/` directory.
 
-2. If you do not have a `native` directory, then you should create one and add the configuration files in the `resources/META_INF/native-image/<group-id>/<artifact-id>/` directory, build and add the native jar to the library by specifying the dependency in the `Ballerina.toml`.
+2. If you do not have a `native` directory, then you should create one and add the configuration files in the `src/main/resources/META-INF/native-image/<group-id>/<artifact-id>/` directory, build and add the native jar to the library by specifying the dependency in the `Ballerina.toml`.
 
 ### Mark the library as GraalVM compatible