aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorredmatrix <mike@macgirvin.com>2016-08-27 19:43:55 -0700
committerredmatrix <mike@macgirvin.com>2016-08-27 19:43:55 -0700
commitf2ff6f394ba993bafd65d49939853f4dabb53dc3 (patch)
treed58ba172701f29903c755713419f63f674c3c4b8
parent391d7fed523b47e9cceb2f27be7c91bdf47b535c (diff)
downloadvolse-hubzilla-f2ff6f394ba993bafd65d49939853f4dabb53dc3.tar.gz
volse-hubzilla-f2ff6f394ba993bafd65d49939853f4dabb53dc3.tar.bz2
volse-hubzilla-f2ff6f394ba993bafd65d49939853f4dabb53dc3.zip
minor (non-technical) corrections in the plugin doc
-rw-r--r--doc/Plugins.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/Plugins.md b/doc/Plugins.md
index 90ff0fb7d..4147d08fd 100644
--- a/doc/Plugins.md
+++ b/doc/Plugins.md
@@ -246,7 +246,7 @@ we will create an argc/argv list for use by your module functions
***Porting Friendica Plugins***
-The $Projectname uses a similar plugin architecture to the Friendica project. The authentication, identity, and permissions systems are completely different. Many Friendica can be ported reasonably easily by renaming a few functions - and then ensuring that the permissions model is adhered to. The functions which need to be renamed are:
+The $Projectname uses a similar plugin architecture to the Friendica project. The authentication, identity, and permissions systems are completely different. Many Friendica plugins can be ported reasonably easily by renaming a few functions - and then ensuring that the permissions model is adhered to. The functions which need to be renamed are:
* Friendica's pluginname_install() is pluginname_load()
@@ -258,6 +258,6 @@ The $Projectname has _install and _uninstall functions but these are used differ
* Friendica's "plugin_settings_post" hook is called "feature_settings_post"
-Changing these will often allow your plugin to function, but please double check all your permission and identity code because the concepts behind it are completely different in the $Projectname. Many structured data names (especially DB schema columns) are also quite different.
+Changing these will often allow your plugin to function, but please double check all your permission and identity code because the concepts behind it are completely different in $Projectname. Many structured data names (especially DB schema columns) are also quite different.
#include doc/macros/main_footer.bb;