diff --git a/i2p2www/pages/site/docs/applications/embedding.html b/i2p2www/pages/site/docs/applications/embedding.html index 4ad3f1e6..2ccabad2 100644 --- a/i2p2www/pages/site/docs/applications/embedding.html +++ b/i2p2www/pages/site/docs/applications/embedding.html @@ -218,7 +218,7 @@ but this isn't advised unless your application makes sure the system clock is co

{% trans %}Choose What and How you Bundle{% endtrans %}

{% trans -%} At a minimum you will need i2p.jar, router.jar, streaming.jar, and mstreaming.jar. -You may omit the two straming jars for a datagram-only app. +You may omit the two streaming jars for a datagram-only app. Some apps may need more, e.g. i2ptunnel.jar or addressbook.jar. Don't forget jbigi.jar, or a subset of it for the platforms you support, to make the crypto much faster. We are currently building them for Java 6, as of 0.9.14. The source is mostly compatible with Java 5 if you want to do your own compile, @@ -305,7 +305,7 @@ import net.i2p.router.Router;

{% trans -%} This code is for the case where your application starts the router, as in our Android app. -You could also have the router start the applictaion via the clients.config and i2ptunnel.config files, +You could also have the router start the application via the clients.config and i2ptunnel.config files, together with Jetty webapps, as is done in our Java packages. As always, state management is the difficult part.