Merge pull request #735 from creativecommons/whitespace-cleanup

Clean-up whitespace

content/blog/entries/2019-07-24-cc-search-wp-plugin/contents.lr

@@ -25,7 +25,7 @@ After a while, our plugin was ready. Its temporary name is “WP CC Search plugi
 
 ![Plugin screenshot 1](01.png)
 
-The plugin’s features are:  
+The plugin’s features are:
 - Works in WordPress editor and add a button above the content text area and into the “Add Media” pop-up window.
 - Via a pop-up window, allows searching through millions of images using Creative Commons Catalog API power.
 - Allows filtering by a provider
@@ -47,11 +47,11 @@ After the plugin’s activation, when the user writes a post, an **“Image with
 
 ![Plugin screenshot 2](02.png)
 
-By pressing the button, a pop-up window allows the user to search using Latin characters for an image. 
+By pressing the button, a pop-up window allows the user to search using Latin characters for an image.
 
 ![Plugin screenshot 3](03.png)
 
-The user can browse the returned images, preview an image and its license and adjust the image settings:  
+The user can browse the returned images, preview an image and its license and adjust the image settings:
 - use of thumbnail or original image
 - set the image link (if any)
 - insert the image into the post or as the featured image
@@ -66,17 +66,17 @@ After the user selects an image and insert it, into the post, the image code alo
 
 The plugin uses AJAX requests to communicate with https://api.creativecommons.engineering and get responses in JSON format.
 
-Only 2 AJAX requests are sent to <https://api.creativecommons.engineering>.  
+Only 2 AJAX requests are sent to <https://api.creativecommons.engineering>.
 1. <https://api.creativecommons.engineering/statistics/image?format=json>, for getting the providers list. Then the JSON response is used as select options, for the provider’s dropdown menu.
 2. A call to <https://api.creativecommons.engineering/image/search> with the necessary parameters for searching for images based on the given words and the selected provided.
 
 The JSON results, are then transformed via jQuery to images and show up into the popup window. When the user selects an image, jQuery creates a complete HTML <div> tag with all the image info and auto add it into the post editor area or executed the WordPress code to use in as featured image.
 
 #### Still to do
 
-There are still some things that we want to add/change into the plugin and any help on building them is welcome.  
+There are still some things that we want to add/change into the plugin and any help on building them is welcome.
 - Find a different plugin name :-). We believe that the plugin’s name should change since it is not an “official” CC commons plugin.
-- Currently, the plugin needs the Classic Editor plugin in order to work for WP 5+. A main goal is to make it Gutenberg compatible. 
+- Currently, the plugin needs the Classic Editor plugin in order to work for WP 5+. A main goal is to make it Gutenberg compatible.
 - Add Multiple images select support
 - Add Multi-select options for filtering: providers
 - Add select options for filtering: licenses, creator
@@ -97,11 +97,11 @@ There are still some things that we want to add/change into the plugin and any h
 
 #### More about us
 
-<span id="footnote-1"></span>**[1] CTI - Greek School Network and Networking Technologies Directorate**  
+<span id="footnote-1"></span>**[1] CTI - Greek School Network and Networking Technologies Directorate**
 Our main activities in Greek School Network and Networking Technologies Directorate (GSN-NTS) (<http://nts.cti.gr>) of Computer Technology Institute and Press “Diophantus” (CTI) are the design, implementation, and support of network infrastructures and Internet services. Through its involvement in pioneer National and European research and development projects, GSN-NTS has a major role in the development of network infrastructures and services, and Internet services as well in Greece, especially those concerning school networks and ICT infrastructures at schools.
 
-<span id="footnote-2"></span>**[2] Greek School Network (<https://www.sch.gr/>)**  
+<span id="footnote-2"></span>**[2] Greek School Network (<https://www.sch.gr/>)**
 <https://www.sch.gr/> is the national network of the Ministry of Education and Religious Affairs which safely interconnects all schools of Primary and Secondary education, including educational units abroad, services and entities supervised by the Ministry of Education and Religious Affairs at central and regional level, service providers of lifelong learning, students, teaching staff, other educators and other entities of Ministry of Education and Religious Affairs ([www.minedu.gov.gr](https://www.minedu.gov.gr/)).
 
-<span id="footnote-3"></span>**[3] <https://blogs.sch.gr>**  
+<span id="footnote-3"></span>**[3] <https://blogs.sch.gr>**
 The plugin was originally developed for <https://blogs.sch.gr>, which is the free blogging platform for all Greek teachers, students, and school units. The blogs.sch.gr is a service of Greek School Network**<sup><a href="#footnote-2">[2]</a></sup>** (https://www.sch.gr/en). It hosts more than 50.000 blogs and users. It is built and maintained by the Greek School Network and Networking Technologies Directorate of CTI.

content/blog/entries/2019-09-11-google-docs-plugin/contents.lr

@@ -17,7 +17,7 @@ A few years ago I published a [Google Docs Add-on that allowed users to insert a
 
 ### Why
 
-I created the add-on after inspiration from students in one of the classes I teach at [Fresno Pacific University’s Graduate School of Education](http://www.fresno.edu/). I was teaching a course on digital literacy, and open licenses and fair use was a large portion of the course. 
+I created the add-on after inspiration from students in one of the classes I teach at [Fresno Pacific University’s Graduate School of Education](http://www.fresno.edu/). I was teaching a course on digital literacy, and open licenses and fair use was a large portion of the course.
 
 To get started, I used the [templates Google provided about building an addon](https://developers.google.com/apps-script/overview), took a look at the html etc on the Creative Commons License Chooser page itself, and eventually got something working! It took a couple of days off and on and mostly was me remembering javascriptI admit I had to pay a guy on Upwork to help clean up the code before I published it because sometimes the chooser would keep selecting hundreds of license images… of course, this was also before I was a bona fide contributor to the open source project I Product Manage, [OpenSALT](http://www.github.com/opensalt/opensalt).
 
@@ -27,13 +27,13 @@ My nine year teaching career in Fresno Unified School District plus my career in
 
 ### What
 
-This month I’ve finally updated it from the old Google Docs add-on store to the Gsuite Marketplace and updated some links. I’ve also updated the [Github sit](https://github.com/brandonopened/creativecommons_gdocs)e as the main website for the app and hope to implement some changes based on the work in[ this Github repo](https://github.com/creativecommons/cc-license-chooser) with an updated license chooser process etc. The add-on has been installed thousands of times and usually has couple of hundred uses a month based on statistics. 
+This month I’ve finally updated it from the old Google Docs add-on store to the Gsuite Marketplace and updated some links. I’ve also updated the [Github sit](https://github.com/brandonopened/creativecommons_gdocs)e as the main website for the app and hope to implement some changes based on the work in[ this Github repo](https://github.com/creativecommons/cc-license-chooser) with an updated license chooser process etc. The add-on has been installed thousands of times and usually has couple of hundred uses a month based on statistics.
 
-I hope in the future to use an API call to support different languages, and perhaps embed RDF into the Google doc if that is possible to make the license machine-searchable. This is a fun project that is useful and helping teach me more about coding and best practices for open source software. 
+I hope in the future to use an API call to support different languages, and perhaps embed RDF into the Google doc if that is possible to make the license machine-searchable. This is a fun project that is useful and helping teach me more about coding and best practices for open source software.
 
 ### How
 
-1. In Google Docs, select “Get Add-ons” 
+1. In Google Docs, select “Get Add-ons”
 
 ![How-to screenshot 1](image2.png)
 
@@ -51,9 +51,9 @@ I hope in the future to use an API call to support different languages, and perh
 [A video tutorial is available here](https://youtu.be/sQZFlNXEVZ4) or by clicking on the image below.
 
 <a href="http://www.youtube.com/watch?feature=player_embedded&v=sQZFlNXEVZ4
-" target="_blank"><img src="https://img.youtube.com/vi/sQZFlNXEVZ4/0.jpg" 
+" target="_blank"><img src="https://img.youtube.com/vi/sQZFlNXEVZ4/0.jpg"
 alt="Video tutorial" border="10" /></a>
 
----  
+---
 
 [No rights reserved](http://creativecommons.org/publicdomain/zero/1.0/) for the content of this blog post by the author.

content/blog/entries/2019-11-25-empowering-collaboration/contents.lr

@@ -42,7 +42,7 @@ the following strategies:
 
 - Participate in social media networks to actively recruit groups who are
   underrepresented in FOSS (free and open source software)
-- Collect anonymous demographic data 
+- Collect anonymous demographic data
 
 A couple of organization examples:
 

content/blog/entries/2020-03-05-involucrate-gsoc-outreachy-es/contents.lr

@@ -14,7 +14,7 @@ body:
 
 En Creative Commons creemos firmemente en que el código abierto es una gran herramienta para fomentar y desarrollar productos con un enfoque comunitario y, a su vez, la consolidación de una comunidad activa de contribuyentes al  patrimonio común (o, en inglés, *Commons*).
 
-Con el fin de fomentar la participación de estudiantes en nuestros proyectos de código abierto, CC es parte de los programas que ofrece Google  ([Google Summer of Code](https://summerofcode.withgoogle.com/)) y también [Outreachy](https://www.outreachy.org/). En ambos casos, el objetivo es involucrar a estudiantes en el código abierto. Para ello, hacemos un llamado abierto a todos y todas quienes tengan interés en colaborar con nuestro equipo, de postular a los llamados cuanto antes. 
+Con el fin de fomentar la participación de estudiantes en nuestros proyectos de código abierto, CC es parte de los programas que ofrece Google  ([Google Summer of Code](https://summerofcode.withgoogle.com/)) y también [Outreachy](https://www.outreachy.org/). En ambos casos, el objetivo es involucrar a estudiantes en el código abierto. Para ello, hacemos un llamado abierto a todos y todas quienes tengan interés en colaborar con nuestro equipo, de postular a los llamados cuanto antes.
 
 #### Google Summer of Code
 Programa impulsado por Google el cual existe desde el año 2005 el cual ha impulsado a mas de 15.000 estudiantes de mas de 118 paises a involucrarse con diversas organizaciones que abogan por el código abierto.

content/blog/entries/2022-12-16-new-to-working-in-open/contents.lr

@@ -13,7 +13,7 @@ body:
 I began working at Creative Commons (CC) as the Full Stack Engineer this year
 and it’s been amazing to get to work in the open at CC. But as someone who
 has been working in closed, internal source environments for a very long
-time it’s definitely been a learning experience and a perspective shift. 
+time it’s definitely been a learning experience and a perspective shift.
 
 For years I benefited from, observed, and offered up personal work into the
 world of open source, but I was never deeply involved in other projects in
@@ -27,7 +27,7 @@ larger community of contributors around the world.
 It's been refreshing and rewarding, but it's also been enlightening. There's
 so much that's different now. Working in the open doesn't just shift the
 terms under which your code is licensed or how many people can contribute, it
-requires a significant shift in both approach and process. 
+requires a significant shift in both approach and process.
 
 For example, working in the open means that while there may be community members
 eager to contribute they may lack contextual understanding that someone more
@@ -44,7 +44,7 @@ documentation about the codebase, as well as detailed known issues, roadmaps,
 etc. All of it needs to be documented and written out, which not only
 benefits the community contributors, but also benefits the project as a
 whole. It means key information has to live in the open alongside the code
-it informs. It's truly a win-win all around. 
+it informs. It's truly a win-win all around.
 
 The process also has to shift, you can't just make a list of things you want to
 tackle and get to work, you have to consider how each item can be smoothly
@@ -58,11 +58,11 @@ view on the overall roadmap and goals the project hopes to meet.
 If you are the steward of a codebase any task list you create or *issues* you
 identify are ultimately not just for you alone. Putting an item on your list
 when you're working alone isn't enough, you've also got to find time to work
-on that item, and work your way through completing it. 
+on that item, and work your way through completing it.
 
 In the open source context, working with a community of contributors, creating
 an *issue* is just as important and meaningful as writing code, in many cases
-it might actually be MORE important. Because *issues* are often the way in 
+it might actually be MORE important. Because *issues* are often the way in
 which contributors first offer up help and insight, they're the first contact
 they have with your project. Furthermore, any *issue* you create may end up
 getting completed by one or more people that are not you, which means it

content/blog/entries/2023-02-01-outreachy-mid-point/contents.lr

@@ -24,6 +24,6 @@ However, there were some project goals that took longer than expected to complet
 
 Additionally, I had to prioritize certain tasks over others and make adjustments to my plan as necessary.
 
-The new CSS I have written so far already makes the website's layout responsive. I have also created a new script.js file and started working on the neccessary functionalities of the website. I plan to implement all feedback gotten from my mentors and debug any remaining issues. Additionally, I will be working on improving the website's overall performance by implementing several optimization techniques as necessary. 
+The new CSS I have written so far already makes the website's layout responsive. I have also created a new script.js file and started working on the neccessary functionalities of the website. I plan to implement all feedback gotten from my mentors and debug any remaining issues. Additionally, I will be working on improving the website's overall performance by implementing several optimization techniques as necessary.
 
 Overall, My aim is to ensure that the website is fully functional and user-friendly for all users.

content/blog/entries/2023-08-25-machine-layer/contents.lr

@@ -83,7 +83,7 @@ systems.
 - **Updated License Information**:
   -  License information has been updated to reflect the latest permissions and
      restrictions. This ensures users and systems are informed accurately.
-- **Alignment with RDF Best Practices**: 
+- **Alignment with RDF Best Practices**:
   - Changes align the representation with RDF best practices. This boosts
     interoperability and compatibility, thanks to standardized namespaces,
      consistent naming, and proper relationship definitions.

content/blog/entries/add-new-sections-descriptions-help-texts-code-examples-schemas-and-serializers/contents.lr

@@ -20,17 +20,17 @@ Welcome to my third blog entry! For week 5 and 6, I added new sections, descript
 
 
 ### Week 5
-For this week, I managed to add a lot of stuff into the documentation. 
-I figured out how to add help texts to classes and how to create serializers. 
-I also managed to move all code examples under response samples. 
-In order to do this, I created a new class called CustomAutoSchema to add [x-code-samples](https://github.com/Redocly/redoc/blob/master/docs/redoc-vendor-extensions.md#x-codesamples). 
-Other stuff that I did include creating new sections such as “Register and Authenticate” and “Glossary”. 
+For this week, I managed to add a lot of stuff into the documentation.
+I figured out how to add help texts to classes and how to create serializers.
+I also managed to move all code examples under response samples.
+In order to do this, I created a new class called CustomAutoSchema to add [x-code-samples](https://github.com/Redocly/redoc/blob/master/docs/redoc-vendor-extensions.md#x-codesamples).
+Other stuff that I did include creating new sections such as “Register and Authenticate” and “Glossary”.
 The hardest part of this week is probably trying to figure out how to add request body examples and move code examples.
 
 
 ### Week 6
 
-For week 6, I added another section called Contribute that provides a todolist to start contributing on Github. 
+For week 6, I added another section called Contribute that provides a todolist to start contributing on Github.
 I also wrote and published this blog post.
 
 ----

content/blog/entries/add-query-using-curl-command-and-provide-response-samples/contents.lr

@@ -23,7 +23,7 @@ So, the first two weeks of Google Season of Docs have passed. For the first week
 
 ### Week 2
 
-For the second week, I started to write response samples. It was tough as I have a hard time understanding [drf-yasg](https://github.com/axnsan12/drf-yasg), which is an automatic Swagger generator. It can produce Swagger / OpenAPI 2.0 specifications from a Django Rest Framework API. I tried to find as many examples as I could to increase my understanding. Funny, but it took me awhile to realise that drf-yasg is not made up of random letters. The DRF part stands for Django Rest Framework while YASG stands for Yet Another Swagger Generator. 
+For the second week, I started to write response samples. It was tough as I have a hard time understanding [drf-yasg](https://github.com/axnsan12/drf-yasg), which is an automatic Swagger generator. It can produce Swagger / OpenAPI 2.0 specifications from a Django Rest Framework API. I tried to find as many examples as I could to increase my understanding. Funny, but it took me awhile to realise that drf-yasg is not made up of random letters. The DRF part stands for Django Rest Framework while YASG stands for Yet Another Swagger Generator.
 
 ----
 

content/blog/entries/add-response-samples-and-descriptions-for-api-endpoints/contents.lr

@@ -19,17 +19,17 @@ Well, hello again 👋! For week 3 and week 4, I added response samples and desc
 
 ### Week 3
 
-Week 3 was quite hectic. I moved back to my hometown during week 3. 
-Took 3 days off to settle my stuff and set up a workspace. 
-I worked on my GSoD project for only 2 days, Monday and Tuesday. 
-I managed to create response samples for most API endpoints. 
+Week 3 was quite hectic. I moved back to my hometown during week 3.
+Took 3 days off to settle my stuff and set up a workspace.
+I worked on my GSoD project for only 2 days, Monday and Tuesday.
+I managed to create response samples for most API endpoints.
 Had a monthly video call with Kriti this week.
 
 ### Week 4
 
-For this week, I reviewed what I’ve done and what I haven’t to estimate new completion time. 
-Thank god, I have a buffer week in my GSoD timeline and deliverables. 
-So yeah, all is good in terms of completion time. 
+For this week, I reviewed what I’ve done and what I haven’t to estimate new completion time.
+Thank god, I have a buffer week in my GSoD timeline and deliverables.
+So yeah, all is good in terms of completion time.
 I started to write descriptions for API endpoints.
 Submitted first PR and published blog entry.