correct names

Author: Cronus1007

content/archives/old-tech-blog/authors/Ishan-Thilina/contents.lr

@@ -1 +1 @@
-username: ishanthilina
+username: Ishan Thilina

content/archives/old-tech-blog/authors/THanish/contents.lr

@@ -1 +1 @@
-username: mnmtanish
+username: Thanish

content/archives/old-tech-blog/authors/dinishi/contents.lr

@@ -1 +1 @@
-username: dinishi
+username:  Dinishika Weerarathna

content/archives/old-tech-blog/authors/igorlukanin/contents.lr

@@ -1 +1 @@
-username: igorlukanin
+username: Igor Lukanin

content/archives/old-tech-blog/entries/cc-drupal/contents.lr

@@ -14,24 +14,24 @@ body:
 Creative Commons provides vast number of public copyright licenses for people who want to enable free distribution of their work. Creative Commons licenses currently covers over **1.6 billion resources**. These license files are then translated to multiple different languages and ported for [different jurisdictions](https://wiki.creativecommons.org/wiki/CC_Ports_by_Jurisdiction) for international usage. People link to the respective licenses along with their licensed works. These license files are in the form of `html` files, stored in [creativecommons/creativecommons.org](https://github.com/creativecommons/creativecommons.org/tree/master/docroot/legalcode) repo.
 
 ### Problem Statement
-There are currently two Creative Commons (CC) modules for Drupal. CC Lite only offers limited functionality, but the CC module has not been updated for a long time and doesn't support current versions of Drupal. 
+There are currently two Creative Commons (CC) modules for Drupal. CC Lite only offers limited functionality, but the CC module has not been updated for a long time and doesn't support current versions of Drupal.
 
-### Planning 
+### Planning
 *  update the Creative Commons module, referencing and possibly building on Creative Commons lite, to support Drupal 6\
 *  expand its functionality to embed and detect license information for some file uploads.
 
-### Summary 
+### Summary
 The Creative Commons module allows users to assign a Creative Commons license to
-the content of a node, or to specify a site-wide license. It uses to Creatve 
-Commons API to retrieve up-to-date license information. Licenses are diplayed 
-using a Creative Commons Node License block and the Creative Commons Site 
+the content of a node, or to specify a site-wide license. It uses to Creatve
+Commons API to retrieve up-to-date license information. Licenses are diplayed
+using a Creative Commons Node License block and the Creative Commons Site
 License block. The module also supports some license metadata fields. License
 information is output using ccREL RDFa inside the blocks, and can optionally be
 output as RDF/XML in the body of a node.
 
 Creative Commons search is available at /search/creativecommons/, and (if the
 Views module is installed and enabled) a Creative Commons view is available at
-/creativecommons. Creative Commons license information and metadata are 
+/creativecommons. Creative Commons license information and metadata are
 available to the Views module.
 
 For a full description of the module, visit the project page:
@@ -46,13 +46,13 @@ None
 ### Installation
 * Install as usual, see http://drupal.org/node/70151 for further information.
 
-### Configuration 
+### Configuration
 * Configure user permissions in Administer >> User management >> Permissions >>
   creativecommons module:
 
   - administer creative commons
 
-    Users can customize the module settings in Administer >> Settings >> 
+    Users can customize the module settings in Administer >> Settings >>
     Creative Commons
 
   - attach creative commons
@@ -68,21 +68,20 @@ None
   Administer >> Settings >> Creative Commons. To make it mandatory to specify a
   license, simply make the 'None' type unavailable.
 
-* Set default license type and jurisdiction in Administer >> Settings >> 
+* Set default license type and jurisdiction in Administer >> Settings >>
   Creative Commons >> site defaults. Here, you can set the default license to be
   used as a site-wide license if you wish, and you can include any relevant
   metadata.
 
 * Enable Creative Commons licensing for desired content types in Administer >>
-  Settings >> Creative Commons >> content types. For example, you might wish to 
+  Settings >> Creative Commons >> content types. For example, you might wish to
   allow Creative Commons licensing for blog posts, but not forum posts.
 
 * In your Drupal user account settings, you can set a jurisdiction or default
   license to override the site defaults.
 
 
-CC Drupal is only possible due to the support and guidance of my mentors [Kevin Reynen](http://drupal.org/user/48877) and `CC Tech Staff Member`, who have been very supportive on every step of the project. Also I would like to thank engineering director [Kriti Godey](https://creativecommons.org/author/kgodey) for her continuous support.
-
+CC Drupal is only possible due to the support and guidance of my mentors [Kevin Reynen](http://drupal.org/user/48877) and `CC Tech Staff Member`, who have been very supportive on every step of the project.
 
 The project is approaching its completion. Can't wait to see it in production.
 

content/archives/old-tech-blog/entries/cc-libreoffice-plugin-updates/contents.lr

@@ -11,7 +11,7 @@ author: Ishan-Thilina
 body:
 
 This year Creative Commons has a much more limited focus on what we would like to see out of Google Summer of Code than in previous years.
-### Installation 
+### Installation
 The latest version of the plugin is 0.7.0, available for download from the [OpenOffice.org Extension site](https://extensions.openoffice.org/en/project/ccooo)
 To install:
 
@@ -32,15 +32,14 @@ The Python port of the Creative Commons Add-in for LibreOffice and OpenOffice.or
 
 For more information visit [the official addin page](https://wiki.creativecommons.org/wiki/OpenOfficeOrg_Addin) of Creative Commons
 
-###Testing 
+###Testing
 Download the out.oxt file. Install it via the LibreOffice Extension Manager (Tools --> Extension Manager).
 
 Then go to `Insert` `--> ` `Creative Commons`. By using the first option you can insert the license information to the document. The second option is for changing those data.
 ### Knowledge Prerequisite
-`Python` ,`Shell` 
-
-CC LibreOffice is only possible due to the support and guidance of  `CC tech staff member`, who have been very supportive on every step of the project. Also I would like to thank engineering director [Kriti Godey](https://creativecommons.org/author/kgodey) for her continuous support.
+`Python` ,`Shell`
 
+CC LibreOffice is only possible due to the support and guidance of  `CC tech staff member`, who have been very supportive on every step of the project.
 The project is approaching its completion. Can't wait to see it in production.
 
 ---

content/archives/old-tech-blog/entries/cc-media-fingerprinting-library/contents.lr

@@ -40,7 +40,7 @@ Some reading:
 ### Knowledge Prerequisite
 `Media formats/encodings` ,`JavaScript` ,`C/C++.`
 
-CC MEDIA FINGERPRINTING LIBRARY is only possible due to the support and guidance of my mentors [Dan Mills](#) or ` other CC tech staff member`, who have been very supportive on every step of the project. Also I would like to thank engineering director [Kriti Godey](https://creativecommons.org/author/kgodey) for her continuous support.
+CC MEDIA FINGERPRINTING LIBRARY is only possible due to the support and guidance of my mentors [Dan Mills](#) or ` other CC tech staff member`, who have been very supportive on every step of the project.
 
 The project is approaching its completion. Can't wait to see it in production.
 

content/archives/old-tech-blog/entries/cc-openoffice-plugin-updates/contents.lr

@@ -17,10 +17,10 @@ The OpenOffice plug-in for Creative Commons was completed in 2007 as a GSoC proj
 ### Solutions
 Planning to :-
 * update the Creative Commons plug-in for OO.o 3 SDK.
-* Add support for CC0. 
+* Add support for CC0.
 * Improve the UI and add support for OO.o Draw.
 
-CC Open Office Plugin Updates is only possible due to the support and guidance of my mentors [nyergler](https://github.com/nyergler?tab=overview&from=2010-12-01&to=2010-12-31) and `other CC Tech Staff Member`, who have been very supportive on every step of the project. Also I would like to thank engineering director [Kriti Godey](https://creativecommons.org/author/kgodey) for her continuous support.
+CC Open Office Plugin Updates is only possible due to the support and guidance of my mentors [nyergler](https://github.com/nyergler?tab=overview&from=2010-12-01&to=2010-12-31) and `other CC Tech Staff Member`, who have been very supportive on every step of the project.
 
 You can follow the project on: [OpenOfficeOrg Addin](https://wiki.creativecommons.org/wiki/OpenOfficeOrg_Addin).
 

content/archives/old-tech-blog/entries/cc-pasteboard/contents.lr

@@ -23,7 +23,7 @@ No matter who you are, though, feel free to learn more about the work we're doin
 [CC Pasteboard](https://github.com/mnmtanish/pasteboard) aims to solve the problem by using tool like pasteboard that allows teachers to clip portions of webpages and reassemble them into documents (currently using Google Docs), while keeping track of the sources both to be used as references, as well as for later editing (e.g. next year, or by another teacher). This storyboard has a good overview of how we envision the tool being used
 
 
-CC Pasteboard is only possible due to the support and guidance of CC tech staff, who have been very supportive on every step of the project. Also I would like to thank engineering director [Kriti Godey](https://creativecommons.org/author/kgodey) for her continuous support.
+CC Pasteboard is only possible due to the support and guidance of CC tech staff, who have been very supportive on every step of the project.
 
 You can follow the project on Github: [mnmtanish/pasteboard](https://github.com/mnmtanish/pasteboard). You can also join the discussion on `#cc` on [IRC](https://freenode.net/)
 

content/archives/old-tech-blog/entries/cc-wordpress-plugin/contents.lr

@@ -28,7 +28,7 @@ To install the plugin, move the directory you found this file in into the plugin
 
 It is recommended that you choose defaults for license, rights holder and jurisdiction on the "CC License Manager" page in the administration area.
 
-### Licensing 
+### Licensing
 Unless otherwise noted, the code is licensed under the [GNU General Public License, Version 2] [6] or (at your option) any later version. Stylesheets are licensed under a [Creative Commons Zero license] [7].
 
 The included [HTML5lib] [8] is licensed under the The [MIT License] [9].
@@ -45,7 +45,7 @@ For rights holders of the included HTML5lib see the [list of HTML5lib committers
 
 The included Ogg (vorbis/theora) php manipulation library was written by Nicolas Ricquemaque.
 
-* [Tutorial](http://mirrors.creativecommons.org/movingimages/wordpress-cc-plugin-with-subtitles.ogv) 
+* [Tutorial](http://mirrors.creativecommons.org/movingimages/wordpress-cc-plugin-with-subtitles.ogv)
 * [1]( http://creativecommons.org/about/licenses/)
 * [2](http://www.whatwg.org/specs/web-apps/current-work/multipage/grouping-content.html#the-figure-element)
 * [3]( http://wiki.creativecommons.org/RDFa)
@@ -61,7 +61,7 @@ The included Ogg (vorbis/theora) php manipulation library was written by Nicolas
 
 
 CC Wordpress Plugin  is only possible due to the support and guidance of my mentors [
-Matthias Rampke](https://creativecommons.org/author/aldenpage) and `other CC Tech Staff Member`, who have been very supportive on every step of the project. Also I would like to thank engineering director [Kriti Godey](https://creativecommons.org/author/kgodey) for her continuous support.
+Matthias Rampke](https://creativecommons.org/author/aldenpage) and `other CC Tech Staff Member`, who have been very supportive on every step of the project.
 
 You can follow the project on Github: [cc-archive/wordpress-cc-plugin](https://github.com/cc-archive/wordpress-cc-plugin).
 

content/archives/old-tech-blog/entries/rdfa-plugin-for-wordpress/contents.lr

@@ -65,7 +65,7 @@ LocalSettings.php:
 You should also add a line like the following, to set the expiration time
 of the cache, in seconds; this line will cache data for a week:
 
-     `$edgCacheExpireTime = 7 * 24 * 60 * 60;` 
+     `$edgCacheExpireTime = 7 * 24 * 60 * 60;`
 
 You can also set for string replacements to be done on the URLs you call,
 for instance to hide API keys:
@@ -83,7 +83,7 @@ set connection settings as well - see the online documentation for more
 information.
 
 
-CC RDFa Plugin for WordPress is only possible due to the support and guidance of my mentors [Nathan Yergler](https://github.com/nyergler) and `CC Tech Staff Member`, who have been very supportive on every step of the project. Also I would like to thank engineering director [Kriti Godey](https://creativecommons.org/author/kgodey) for her continuous support.
+CC RDFa Plugin for WordPress is only possible due to the support and guidance of my mentors [Nathan Yergler](https://github.com/nyergler) and `CC Tech Staff Member`, who have been very supportive on every step of the project.
 
 You can follow the project on Github: [cc-archive/ExternalData_RDFa](https://github.com/cc-archive/ExternalData_RDFa).