Fix documentation about module-info.java

Author: jwharm

docs/register.md

@@ -37,11 +37,11 @@ When instantiating a new Java instance of the class, the call to `super()` will
 !!! info
     In Java-GI version 0.11.* and below, the GType must be explicitly registered with a call to `Types.register(classname.class)`, and the constructor must be a static factory method. Since Java-GI 0.12.0, this is not necessary anymore.
 
-If your Java application is module-based, you must export your package to the `org.gnome.gobject` module in your `module-info.java` file, to allow the reflection to work:
+If your Java application is module-based, you must "open" your package to the `org.gnome.glib` module in your `module-info.java` file, to allow the reflection to work:
 
 ```
 module my.module.name {
-    exports my.package.name to org.gnome.gobject;
+    opens my.package.name to org.gnome.glib;
 }
 ```
 

docs/templates.md

@@ -44,11 +44,11 @@ A class with a `@GtkTemplate` annotation will be registered as a Gtk composite t
 
 In the above class, the `header_bar` and `label` fields and the `buttonClicked` callback function are all declared the UI file. During class initialization, the fields are set to the associated widget.
 
-Because the registration of composite template classes uses reflection, you must add the following `exports` statement to your `module-info.java` file:
+If you use Java modules (with a `module-info.java`), add the following `opens` statement to `module-info.java` to allow Java-GI's reflection to work:
 
 ```
 module my.module.name {
-    exports my.package.name to org.gnome.gobject,org.gnome.gtk;
+    opens my.package.name to org.gnome.glib,org.gnome.gtk;
 }
 ```