FINERACT-2067: (doc) fix some typos in fineract-doc module.

2024-03-19 13:42:45 +01:00
parent d955bc26cb
commit 6b94192ac6
19 changed files with 30 additions and 30 deletions
@@ -21,7 +21,7 @@ To be able to send emails via SMTP with your GMail account you probably need to
 5. 2-Step Verification is only set up for security keys.
 6. Your account is through work, school, or other organization.
 7. You turned on Advanced Protection.
-8. At the bottom, choose Select app and choose the app you using and then Select device and choose the device you're using and then Generate.
+8. At the bottom, choose Select app and choose the app you're using and then Select device and choose the device you're using and then Generate.
 9. Follow the instructions to enter the App Password. The App Password is the 16-character code in the yellow bar on your device.
 10. Tap Done.

@@ -176,7 +176,7 @@ gpg --export-secret-keys --armor aleks@apache.org > privkey.asc
 +
 Your private key should be kept in a safe place, like an encrypted flash drive. Treat it like your house key. Only you can have it and don't lose it. And you must remember your passphrase, otherwise you can't unlock your private key.
 +
-You should protect your revocation certificate. Anyone in posession of your revocation certificate, could immediately revoke your public/private key pair and generate fake ones.
+You should protect your revocation certificate. Anyone in possession of your revocation certificate, could immediately revoke your public/private key pair and generate fake ones.

 IMPORTANT: Please contact a PMC member to add your GPG public key in Fineract's Subversion repository. This is necessary to be able to validate published releases.

@@ -194,7 +194,7 @@ Before doing this, make sure that your default keyserver is hkp://keyserver.ubun
 keyserver hkp://keyserver.ubuntu.com/
 ----
 +
-Alternatively you can provide the keyserver whith the send command:
+Alternatively you can provide the keyserver with the send command:
 +
 [source,bash]
 ----
@@ -20,7 +20,7 @@ fineract.config.username=aleks <4>
 fineract.config.password=******
 ----
 <1> Make sure you use the full GPG key name (you can list yours via `gpg --list-secret-keys --keyid-format=long`)
-<2> GnuPG has it's own kbx format to store the public key ring. At the moment we are only supporting this format
+<2> GnuPG has its own kbx format to store the public key ring. At the moment we are only supporting this format
 <3> Currently we only have instructions for GMail
 <4> Apache committer credentials

@@ -4,7 +4,7 @@

 The RM should, if one doesn't already exist, first create a new release umbrella issue in JIRA. This issue is dedicated to tracking (a summary of) any discussion related to the planned new release. An example of such an issue is FINERACT-873 - Release Apache Fineract v1.4.0 RESOLVED.

-The RM then creates an list of resolved issues & features through an initial check in JIRA for already resolved issues for the release, and then setup a timeline for release branch point. The time for the day the issue list is created to the release branch point must be at least two weeks in order to give the community a chance to prioritize and commit any last minute features and issues they would like to see in the upcoming release.
+The RM then creates a list of resolved issues & features through an initial check in JIRA for already resolved issues for the release, and then setup a timeline for release branch point. The time for the day the issue list is created to the release branch point must be at least two weeks in order to give the community a chance to prioritize and commit any last minute features and issues they would like to see in the upcoming release.

 The RM must then send the pointer to the umbrella issue along with the tentative timeline for branch point to the developer lists. Any work identified as release related that needs to be completed should be added as a sub tasks of the umbrella issue to allow all developers and users to see the overall release progress in one place. The umbrella issue shall also link to any issues still requiring clarification whether or not they will make it into the release.