reformatting to add trailing dot

content/docs/org/about-us/_index.md

@@ -6,22 +6,22 @@ bookToc: false
 
 <h1>based</h1>
 
-**writing** is one of your best mediums to learn or share something with others. **inspired** by [Hak5](https://hak5.org/), we also intend to develop our in-house tools and payloads relevant to the security industry. **by** building such a community-driven platform, we hope all of the contents within this platform can be of good use for others to benefit from. **which** is kinda cool
+**writing** is one of your best mediums to learn or share something with others. **inspired** by [Hak5](https://hak5.org/), we also intend to develop our in-house tools and payloads relevant to the security industry. **by** building such a community-driven platform, we hope all of the contents within this platform can be of good use for others to benefit from. **which** is kinda cool.
 
 
 {{< columns >}}
 <h2>/ˈvɪʒ.ən/</h2>
 
-**our** vision is to become one of the go-to platforms of choice for others to search similar cases or problems about infosec in general or even to try out and develop pentesting tools & payloads for our community-based arsenal
+**our** vision is to become one of the go-to platforms of choice for others to search similar cases or problems about infosec in general or even to try out and develop pentesting tools & payloads for our community-based arsenal.
 <--->
 <h2>/ˈmɪʃ.ən/</h2>
 
-**our** mission is to support the interest in publishing content for others to help the public awareness of information security in this digital world as a form of giving back to the community
+**our** mission is to support the interest in publishing content for others to help the public awareness of information security in this digital world as a form of giving back to the community.
 {{< /columns >}}
 
 <h2 align="center" style="margin: 16px 0px;">bastions</h2>
 <p align="center">
-<strong>here</strong> are some of the peeps that helped to build this platform to the way it is now, a hopefully-functioning site in society. <strong>hop</strong> onto the <a href="/docs/org/contribution/">contribution</a> tab to learn how your role can help this platform grows even better too
+<strong>here</strong> are some of the peeps that helped to build this platform to the way it is now, a hopefully-functioning site in society. <strong>hop</strong> onto the <a href="/docs/org/contribution/">contribution</a> tab to learn how your role can help this platform grows even better too.
 
 </p>
 
@@ -35,7 +35,7 @@ bookToc: false
 <h1 style="margin: 32px 0px 16px;">JKT ッ ID</h1>
 
 <p style="margin-bottom: 0;"><strong>N</strong> 6°17'1.746" | <strong>S</strong> 106°48'17.507" <br>
-<span><strong>hotpotcookie</strong>@proton.me</span></p>
+<span><strong>hotpotcookie.gg</strong>@gmail.com</span></p>
 
 <p style="margin-top: -0.4em; margin-bottom: 0; font-size: 0.85em;">
 	<a style="text-decoration: none;" href="https://www.instagram.com/hotpotcookie" target="_blank" rel="noopener noreferrer"><span style="font-size: 1em; color: #ff79c6; font-weight: bold;">instagram</span></a> //

content/docs/org/contribution/_index.md

@@ -6,20 +6,20 @@ bookToc: false
 
 <h1>thank you kind sir</h1>
 
-**as** an open-source organization, *hotpotcookie* site offers three main contents for you to share your cool and edgy ideas of contents to the readers, which are [blog](/posts/blog), [paper](/posts/paper), and [write-up](/posts/writeup). **your** submission will take place online on our site at least within 48 hours after your ```commit``` since it requires proofreading from our internal team. **as** for the [payloads](/docs/gg/payload/) and [pentest tool](/docs/gg/pentest-tool/), it's going to be reviewed & tested first in a local lab within a whole week before merging it to the main arsenal
+**as** an open-source organization, *hotpotcookie* site offers three main contents for you to share your cool and edgy ideas of contents to the readers, which are [blog](/posts/blog), [paper](/posts/paper), and [write-up](/posts/writeup). **your** submission will take place online on our site at least within 48 hours after your ```commit``` since it requires proofreading from our internal team. **as** for the [payloads](/docs/gg/payload/) and [pentest tool](/docs/gg/pentest-tool/), it's going to be reviewed & tested first in a local lab within a whole week before merging it to the main arsenal.
 
 ## consider the following
 
 **since** all the contributions are based on your pull request, here are some things that you need to consider for the content of your submissions to meet our baseline template: 
 
 - **the** submission should be written in a ```.md``` format
 - **what** count as a contribution are creating content, fixing bugs & typos, or adding any minor or major significant improvement
-- **submitted** images should be in a ```.webp``` format, ideally less than around ```100,0 KiB``` collectively for a single post. **the** naming template for those images should be defined by the post's ```id```, such as ```[post-id]-[n].webp``` with ```[n]``` as the n-th images that you provided and stored in ```/main/static/images/data/[content]/```
-- **the** usage of [asciinema](https://asciinema.org/) are preferable as it gives clarity to the context of what the commands are cookin
+- **submitted** images should be in a ```.webp``` format, ideally less than around ```800,0 KiB``` collectively for a single post. **the** naming template for those images should be defined by the post's ```id```, such as ```[post-id]-[n].webp``` with ```[n]``` as the n-th images that you provided and stored in ```/main/static/images/data/[content]/```
+- **the** usage of [asciinema](https://asciinema.org/) with [agg](https://github.com/asciinema/agg) are preferable as it gives clarity to the context of what the commands are cookin
 
 ## local repository
 
-**once** your have forked [hotpotcookie](https://github.com/hotpotcookie/hotpotcookie) locally, the last thing you wanted to do is to submit the posts via pull requests. **for** a start, we will clone the forked repo and switch the branch from ```main``` to ```contrib```. **your** push on branch ```contrib```, later on, will be merged to the main repository for your posts to live on-site
+**once** your have forked [hotpotcookie](https://github.com/hotpotcookie/hotpotcookie) locally, the last thing you wanted to do is to submit the posts via pull requests. **for** a start, we will clone the forked repo and switch the branch from ```main``` to ```contrib```. **your** push on branch ```contrib```, later on, will be merged to the main repository for your posts to live on-site.
 
 ```markdown
 $ git clone https://github.com/[username]/hotpotcookie.git
@@ -30,7 +30,7 @@ $ git remote add upstream https://github.com/hotpotcookie/hotpotcookie.git
 
 ## markdown template & git staging
 
-**as** we refer from those points before, here are some base ```.md``` template files to give you some contexts for each type of content that you might contribute to, check them out
+**as** we refer from those points before, here are some base ```.md``` template files to give you some contexts for each type of content that you might contribute to, check them out.
 
 {{< hint warning >}}
 **please** verify that each file is placed to the corressponding directory, as it will significantly minimize the work on fixing the file path before rebuilding the site. **you** can follow the commands below on handling each type of file that is going to be staged
@@ -66,7 +66,7 @@ $ git remote add upstream https://github.com/hotpotcookie/hotpotcookie.git
   - [title - site](URL) // list of all the sites that you may cite or use
   - [Introduction to Log4j - **Medium***](https:..) // citation example from the format above
   ```
-  **when** all the needed files are ready, including the post and the images, you can finally stage all those resources and commit it. **here** is the snippet with the relative path to the corresponding files
+  **when** all the needed files are ready, including the post and the images, you can finally stage all those resources and commit it. **here** is the snippet with the relative path to the corresponding files.
 
   ```markdown
 $ git add content/posts/blog/embedding-log4shell-to-badusb-for-rat.md
@@ -83,15 +83,15 @@ $ git commit -m "adding my content with its image resources"
 
 {{< /tabs >}}
 
-**as** for your contribution profile to appearing on the [about us](/docs/org/about-us/) page, you can submit your [villager](https://meiker.io/play/11374/online.html) in ```/main/static/images/profile``` with your [GitHub](https://github.com) username as the file name of it, such as ```[username].webp```. **notice** that this step is one time only, unless you wanted to change it later on
+**as** for your contribution profile to appearing on the [about us](/docs/org/about-us/) page, you can submit your [villager](https://meiker.io/play/11374/online.html) in ```/main/static/images/profile``` with your [GitHub](https://github.com) username as the file name of it, such as ```[username].webp```. **notice** that this step is one time only, unless you wanted to change it later on.
 
 ```markdown
 $ git add static/images/profile/[username].webp
 $ git commit -m "adding my villager avatar"
 ```
 ## pushing your commits
 
-**once** all the files have been staged and committed, the last thing to do is push your commits to the remote branch on the main repository. **that** way, we can review and merge it if it passes the criteria that are mandatory or needed
+**once** all the files have been staged and committed, the last thing to do is push your commits to the remote branch on the main repository. **that** way, we can review and merge it if it passes the criteria that are mandatory or needed.
 
 ```markdown
 $ git push -u origin contrib

content/docs/org/privacy-policy/_index.md

@@ -5,10 +5,11 @@ bookToc: false
 
 <h1>three-way handshake</h1>
 
-**as** white hats, by representing the *hotpotcookie*, we don't disclose any private or credential pieces of information of any parties involved in any form of data aggregation, as this site doesn't collect any user's data. **for** further notice, *hotpotcookie* site is also not integrated with [Google Analytics](https://support.google.com/analytics/answer/10089681) by storing cookies anonymously and will not be intended to
+## data handling
+**as** white hats, by representing the *hotpotcookie*, we don't disclose any private or credential pieces of information of any parties involved in any form of data aggregation, as this site doesn't collect any user's data. **for** further notice, *hotpotcookie* site is also not integrated with [Google Analytics](https://support.google.com/analytics/answer/10089681) by storing cookies anonymously and will not be intended to.
 
 
-**the** below describes from what sources of information, study cases or problems we conducted, which also addresses how we handle that information within this site
+**the** below describes from what sources of information, study cases or problems we conducted, which also addresses how we handle that information within this site.
 
 {{< expand "vendor security flaw" "▼・ᴥ・▼" >}}
 - **we** routinely conduct research into the security of commonly used applications and products that are done to educate and protect end users from the risk behind it
@@ -30,6 +31,11 @@ bookToc: false
 - **when** citing sources from internet sites, we may collect personal information such as the author’s name, website URL, and the date of publication. **that** said, we only collect this information to accurately cite the source and provide proper attribution to the author
 {{< /expand >}}
 
-If you have any questions or concerns about our privacy policy or our handling of your personal information, please contact us using the contact information provided
+## affiliate marketing
+**we** may partner with third-party companies or e-commerces and promote their products or services through affiliate links on our site. **please** note that any information you provide during the purchasing process, such as email address or payment details, is collected and processed by the respective third-party companies, and their privacy policies govern the handling of that information.
+
+**we** encourage you to review the privacy policies of any external websites or services you visit through affiliate links on our website to understand how your information will be handled. **by** using our website and engaging with affiliate links, you acknowledge and accept these terms regarding the privacy and data handling practices related to affiliate marketing.
+
+**if** you have any questions or concerns about our privacy policy or our handling of your personal information, please contact us using the contact information provided
 
 ---