Remove extra lines

carusogabriel · carusogabriel · commit f763070c718a · 2018-01-03T01:31:55.000-02:00
Signed-off-by: Gabriel Caruso &lt;carusogabriel34@gmail.com&gt;
diff --git a/LICENSE-CC.md b/LICENSE-CC.md
@@ -294,7 +294,6 @@ BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
     License is not intended to restrict the license of any rights under
     applicable law.
 
-
 Creative Commons Notice
 
     Creative Commons is not a party to this License, and makes no warranty
diff --git a/README.md b/README.md
@@ -7,7 +7,6 @@ audience is each other, but we’re very aware that the rest of the PHP communit
 is watching. If other folks want to adopt what we’re doing they are welcome to
 do so, but that is not the aim.
 
-
 Proposing a Standard Recommendation
 ------------------------------------
 
@@ -59,7 +58,6 @@ may vary, but it is consistent within the same specification). The PHP FIG does
 offer official translations into other languages but other external entities are free
 to translate the specifications in accordance with the license.
 
-
 Voting Members
 --------------
 
diff --git a/accepted/PSR-1-basic-coding-standard.md b/accepted/PSR-1-basic-coding-standard.md
@@ -12,7 +12,6 @@ interpreted as described in [RFC 2119].
 [PSR-0]: https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-0.md
 [PSR-4]: https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-4-autoloader.md
 
-
 ## 1. Overview
 
 - Files MUST use only `<?php` and `<?=` tags.
@@ -31,7 +30,6 @@ interpreted as described in [RFC 2119].
 
 - Method names MUST be declared in `camelCase`.
 
-
 ## 2. Files
 
 ### 2.1. PHP Tags
@@ -99,7 +97,6 @@ if (! function_exists('bar')) {
 }
 ~~~
 
-
 ## 3. Namespace and Class Names
 
 Namespaces and classes MUST follow an "autoloading" PSR: [[PSR-0], [PSR-4]].
diff --git a/accepted/PSR-11-container-meta.md b/accepted/PSR-11-container-meta.md
@@ -335,7 +335,6 @@ At the time of writing, the following projects already implement and/or consume
 
 This list is not comprehensive and should be only taken as an example showing that there is considerable interest in the PSR.
 
-
 9. People
 ---------
 ### 9.1 Editors
diff --git a/accepted/PSR-13-links.md b/accepted/PSR-13-links.md
@@ -22,7 +22,6 @@ interpreted as described in [RFC 2119](http://tools.ietf.org/html/rfc2119).
 - [IANA Link Relations Registry](http://www.iana.org/assignments/link-relations/link-relations.xhtml)
 - [Microformats Relations List](http://microformats.org/wiki/existing-rel-values#HTML5_link_type_extensions)
 
-
 ## 1. Specification
 
 ### 1.1 Basic links
@@ -42,7 +41,6 @@ specification.
 *    **Serializer** - A library or other system that takes one or more Link objects and produces
 a serialized representation of it in some defined format.
 
-
 ### 1.2 Attributes
 
 All links MAY include zero or more additional attributes beyond the URI and relationship.
@@ -257,7 +255,6 @@ interface EvolvableLinkInterface extends LinkInterface
      */
     public function withAttribute($attribute, $value);
 
-
     /**
      * Returns an instance with the specified attribute excluded.
      *
diff --git a/accepted/PSR-16-simple-cache-meta.md b/accepted/PSR-16-simple-cache-meta.md
@@ -10,15 +10,13 @@ means libraries can drop their own caching implementations and easily rely
 on the one given to them by the framework, or another dedicated cache
 library the user picked.
 
-
 2. Why Bother?
 --------------
 
 PSR-6 solves this problem already, but in a rather formal and verbose way for
 what the most simple use cases need. This simpler approach aims to build a
 standardized layer of simplicity on top of the existing PSR-6 interfaces.
 
-
 3. Scope
 --------
 
@@ -35,7 +33,6 @@ standardized layer of simplicity on top of the existing PSR-6 interfaces.
 
 * Solving all possible edge cases, PSR-6 does this well already.
 
-
 4. Approaches
 -------------
 
@@ -44,7 +41,6 @@ only by the most simple cases. It does not have to be implementable by all
 possible cache backends, nor be usable for all usages. It is merely a layer
 of convenience on top of PSR-6.
 
-
 5. People
 ---------
 
@@ -68,14 +64,12 @@ For being an early reviewer
 
 * Daniel Messenger (@dannym87)
 
-
 6. Votes
 --------
 
 * **Entrance Vote:**  https://groups.google.com/d/topic/php-fig/vyQTKHS6pJ8/discussion
 * **Acceptance Vote:**  https://groups.google.com/d/msg/php-fig/A8e6GvDRGIk/HQBJGEhbDQAJ
 
-
 7. Relevant Links
 -----------------
 
diff --git a/accepted/PSR-16-simple-cache.md b/accepted/PSR-16-simple-cache.md
@@ -115,7 +115,6 @@ Compatibility with them is simply used as a baseline for acceptable object value
 If it is not possible to return the exact saved value for any reason, implementing
 libraries MUST respond with a cache miss rather than corrupted data.
 
-
 # 2. Interfaces
 
 ## 2.1 CacheInterface
diff --git a/accepted/PSR-2-coding-style-guide-meta.md b/accepted/PSR-2-coding-style-guide-meta.md
@@ -9,12 +9,10 @@ The style rules herein are derived from commonalities among the various member p
 collaborate across multiple projects, it helps to have one set of guidelines to be used among all those
 projects. Thus, the benefit of this guide is not in the rules themselves, but in the sharing of those rules.
 
-
 ## 2. Votes
 
 - **Acceptance Vote:** [ML](https://groups.google.com/d/msg/php-fig/c-QVvnZdMQ0/TdDMdzKFpdIJ)
 
-
 ## 3. Errata
 
 ### 3.1 - Multi-line Arguments (09/08/2013)
diff --git a/accepted/PSR-2-coding-style-guide.md b/accepted/PSR-2-coding-style-guide.md
@@ -20,7 +20,6 @@ interpreted as described in [RFC 2119].
 [PSR-0]: https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-0.md
 [PSR-1]: https://github.com/php-fig/fig-standards/blob/master/accepted/PSR-1-basic-coding-standard.md
 
-
 ## 1. Overview
 
 - Code MUST follow a "coding style guide" PSR [[PSR-1]].
@@ -132,8 +131,6 @@ The PHP constants `true`, `false`, and `null` MUST be in lower case.
 
 [keywords]: http://php.net/manual/en/reserved.keywords.php
 
-
-
 ## 3. Namespace and Use Declarations
 
 When present, there MUST be one blank line after the `namespace` declaration.
@@ -159,7 +156,6 @@ use OtherVendor\OtherPackage\BazClass;
 
 ~~~
 
-
 ## 4. Classes, Properties, and Methods
 
 The term "class" refers to all classes, interfaces, and traits.
@@ -372,7 +368,6 @@ The body of each structure MUST be enclosed by braces. This standardizes how
 the structures look, and reduces the likelihood of introducing errors as new
 lines get added to the body.
 
-
 ### 5.1. `if`, `elseif`, `else`
 
 An `if` structure looks like the following. Note the placement of parentheses,
@@ -393,7 +388,6 @@ if ($expr1) {
 The keyword `elseif` SHOULD be used instead of `else if` so that all control
 keywords look like single words.
 
-
 ### 5.2. `switch`, `case`
 
 A `switch` structure looks like the following. Note the placement of
@@ -422,7 +416,6 @@ switch ($expr) {
 }
 ~~~
 
-
 ### 5.3. `while`, `do while`
 
 A `while` statement looks like the following. Note the placement of
@@ -590,7 +583,6 @@ $foo->bar(
 );
 ~~~
 
-
 ## 7. Conclusion
 
 There are many elements of style and practice intentionally omitted by this
@@ -613,7 +605,6 @@ guide. These include but are not limited to:
 Future recommendations MAY revise and extend this guide to address those or
 other elements of style and practice.
 
-
 ## Appendix A. Survey
 
 In writing this style guide, the group took a survey of member projects to
diff --git a/accepted/PSR-4-autoloader-meta.md b/accepted/PSR-4-autoloader-meta.md
@@ -120,7 +120,6 @@ PSR-0, but seeing as their presence in that document is in reference to
 transitioning away from PHP 5.2 and previous pseudo-namespacing, it is
 acceptable to remove them here as well.
 
-
 3. Scope
 --------
 
@@ -141,7 +140,6 @@ acceptable to remove them here as well.
 
 - Provide a general transformation algorithm for non-class resources
 
-
 4. Approaches
 -------------
 
@@ -182,7 +180,6 @@ Cons:
   determine where it is in the file system (the "class-to-file" convention
   inherited from Horde/PEAR).
 
-
 ### 4.2 Alternative: Stay With PSR-0 Only
 
 Staying with PSR-0 only, although reasonable, does leave us with relatively
@@ -199,7 +196,6 @@ Cons:
 - Leaves us with underscores in the class name being honored as directory
   separators
 
-
 ### 4.3 Alternative: Split Up Autoloading And Transformation
 
 Beau Simensen and others suggested that the transformation algorithm might be
@@ -234,7 +230,6 @@ PHP versions before 5.3.3 do not strip the leading namespace separator, so
 the responsibility to look out for this falls on the implementation. Failing
 to strip the leading namespace separator could lead to unexpected behavior.
 
-
 5. People
 ---------
 
@@ -257,7 +252,6 @@ to strip the leading namespace separator could lead to unexpected behavior.
 - Paul Dragoonis
 - Too many others to name and count
 
-
 6. Votes
 --------
 
@@ -273,7 +267,6 @@ to strip the leading namespace separator could lead to unexpected behavior.
 
     - 3rd attempt: TBD
 
-
 7. Relevant Links
 -----------------
 
diff --git a/accepted/PSR-4-autoloader.md b/accepted/PSR-4-autoloader.md
@@ -4,15 +4,13 @@ The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD",
 "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be
 interpreted as described in [RFC 2119](http://tools.ietf.org/html/rfc2119).
 
-
 ## 1. Overview
 
 This PSR describes a specification for [autoloading][] classes from file
 paths. It is fully interoperable, and can be used in addition to any other
 autoloading specification, including [PSR-0][]. This PSR also describes where
 to place files that will be autoloaded according to the specification.
 
-
 ## 2. Specification
 
 1. The term "class" refers to classes, interfaces, traits, and other similar
@@ -56,7 +54,6 @@ to place files that will be autoloaded according to the specification.
 4. Autoloader implementations MUST NOT throw exceptions, MUST NOT raise errors
    of any level, and SHOULD NOT return a value.
 
-
 ## 3. Examples
 
 The table below shows the corresponding file path for a given fully qualified
diff --git a/accepted/PSR-6-cache-meta.md b/accepted/PSR-6-cache-meta.md
@@ -13,7 +13,6 @@ provide the functionality they need. In addition, the developers of caching
 libraries themselves face a choice between only supporting a limited number
 of frameworks or creating a large number of adapter classes.
 
-
 2. Why Bother?
 --------------
 
@@ -202,7 +201,6 @@ function load_widgets(array $ids)
  * be added by extending implementations.
  */
 
-
 interface TaggablePoolInterface extends Psr\Cache\CachePoolInterface
 {
     /**
@@ -293,7 +291,6 @@ do so.
 
 [Acceptance vote on the mailing list](https://groups.google.com/forum/#!msg/php-fig/dSw5IhpKJ1g/O9wpqizWAwAJ)
 
-
 7. Relevant Links
 -----------------
 
diff --git a/accepted/PSR-6-cache.md b/accepted/PSR-6-cache.md
@@ -26,7 +26,6 @@ The goal of this PSR is to allow developers to create cache-aware libraries that
 can be integrated into existing frameworks and systems without the need for
 custom development.
 
-
 ## Definitions
 
 *    **Calling Library** - The library or code that actually needs the cache
@@ -92,7 +91,6 @@ items, such as an object destructor, persisting all on save(), a timeout or
 max-items check or any other appropriate logic. Requests for a cache item that
 has been deferred MUST return the deferred but not-yet-persisted item.
 
-
 ## Data
 
 Implementing libraries MUST support all serializable PHP data types, including:
diff --git a/accepted/PSR-7-http-message.md b/accepted/PSR-7-http-message.md
@@ -57,7 +57,6 @@ interpreted as described in [RFC 2119](http://tools.ietf.org/html/rfc2119).
 - [RFC 7230](http://tools.ietf.org/html/rfc7230)
 - [RFC 7231](http://tools.ietf.org/html/rfc7231)
 
-
 ## 1. Specification
 
 ### 1.1 Messages
diff --git a/bylaws/005-licensing-policies.md b/bylaws/005-licensing-policies.md
@@ -9,7 +9,6 @@ Licensing Policies
    functions, interfaces and procedural code), as well as any code inside of
    examples, tutorials, supporting documents, website code and the PSRs themselves.
 
-
 ## 2. Documentation
 
 All remaining non-code items must be licensed under the Creative Commons BY 3.0
diff --git a/bylaws/006-psr-amendments.md b/bylaws/006-psr-amendments.md
@@ -26,7 +26,6 @@ official PHP FIG GitHub repo `fig-standards`.
 as an alternative.
 > [PSR-4]: http://php-fig.org/psr/psr-4
 
-
 ## 2. Dependencies
 
 As documents are expected to be replaced rather than amended, dependencies on
diff --git a/proposed/event-manager-meta.md b/proposed/event-manager-meta.md
@@ -12,24 +12,16 @@ Event Dispatching allows developer to inject logic into an application easily.
 Many frameworks implement some form of a event dispatching that allows users to
 inject functionality with the need to extend classes.
 
-
 3. Scope
 --------
 
 ### 3.1 Goals
 
-
-
 ### 3.2 Non-Goals
 
-
-
 4. Approaches
 -------------
 
-
-
-
 5. People
 ---------
 
@@ -47,7 +39,6 @@ inject functionality with the need to extend classes.
 
 * **Entrance Vote: **  ADD LINK HERE
 
-
 7. Relevant Links
 -----------------
 
diff --git a/proposed/extended-coding-style-guide.md b/proposed/extended-coding-style-guide.md
diff --git a/proposed/http-client/http-client.md b/proposed/http-client/http-client.md
diff --git a/proposed/phpdoc.md b/proposed/phpdoc.md
diff --git a/proposed/psr-8-hug/PSR-8-hug-meta.md b/proposed/psr-8-hug/PSR-8-hug-meta.md
diff --git a/proposed/psr-8-hug/psr-8-hug.md b/proposed/psr-8-hug/psr-8-hug.md
diff --git a/proposed/security-disclosure-publication-meta.md b/proposed/security-disclosure-publication-meta.md
diff --git a/proposed/security-reporting-process-meta.md b/proposed/security-reporting-process-meta.md
