Unified · Split
| @@ -33,7 +33,7 @@ The `call` method must return either `doc` or `html`, depending on the type of f · 32 unmodified lines | ||
| 33 | 33 | |
| 34 | 34 | * `doc` [Nokogiri::XML::Node] |
| 35 | 35 | The Nokogiri representation of the container element. |
| 36 | − See [Nokogiri's API docs](http://nokogiri.org/Nokogiri/XML/Node.html#methods_nav) for the list of available methods. | |
| 36 | + See [Nokogiri's API docs](http://www.rubydoc.info/github/sparklemotion/nokogiri/Nokogiri/XML/Node) for the list of available methods. | |
| 37 | 37 | |
| 38 | 38 | * `html` [String] |
| 39 | 39 | The string representation of the container element. |
| @@ -97,7 +97,7 @@ Scrapers can have any number of custom filters but require at least the two desc · 57 unmodified lines | ||
| 97 | 97 | |
| 98 | 98 | The `CleanHtml` filter is tasked with cleaning the HTML markup where necessary and removing anything superfluous or nonessential. Only the core documentation should remain at the end. |
| 99 | 99 | |
| 100 | −Nokogiri's many jQuery-like methods make it easy to search and modify elements — see the [API docs](http://nokogiri.org/Nokogiri/XML/Node.html#methods_nav). | |
| 100 | +Nokogiri's many jQuery-like methods make it easy to search and modify elements — see the [API docs](http://www.rubydoc.info/github/sparklemotion/nokogiri/Nokogiri/XML/Node). | |
| 101 | 101 | |
| 102 | 102 | Here's an example implementation that covers the most common use-cases: |
| 103 | 103 | |