fix: i18n adventure example

Author: Lulu13022002

src/content/docs/paper/dev/api/component-api/i18n.md

@@ -45,7 +45,7 @@ some.translation.key=Translated Message: {0}
 ```
 
 ```java
-TranslationStore store = TranslationStore.messageFormat(Key.key("namespace:value"));
+TranslationStore.StringBased<MessageFormat> store = TranslationStore.messageFormat(Key.key("namespace:value"));
 
 ResourceBundle bundle = ResourceBundle.getBundle("your.plugin.Bundle", Locale.US, UTF8ResourceBundleControl.get());
 store.registerAll(Locale.US, bundle, true);
@@ -57,10 +57,10 @@ is created from a bundle located on the classpath with the specified [`Locale`](
 Finally, that `ResourceBundle` is added to the store. That store is then added as a source to the `GlobalTranslator`.
 This makes all the translations available server-side.
 
-Now you can use translation keys in translatable components.
+Now you can use your translation keys in translatable components.
 
 ```java
-final Component message = Component.translatable("some.translation.key", Component.text("The Argument"))
+Component.translatable("some.translation.key", Component.text("The Argument"))
 ```
 
 This will show to clients using the US English language: `Translated Message: The Argument`.