diff options
| author | Ilmari Lauhakangas <ilmari.lauhakangas@libreoffice.org> | 2018-02-09 14:19:29 +0200 |
|---|---|---|
| committer | Adolfo Jayme Barrientos <fitojb@ubuntu.com> | 2018-02-11 01:18:46 +0100 |
| commit | 51cb2e66897a9dd5676b33d35a5683a8f8e56ef5 (patch) | |
| tree | c551127b50547cf7a47bbfdbebcc195c91e8c890 /README.md | |
| parent | 720759ad342000f2729a6c983523af931f01dbef (diff) | |
Updated links in readme files (https etc.)
Change-Id: Id4906290f312dc6d1800d5d17dedf1f07dd3480d
Reviewed-on: https://gerrit.libreoffice.org/49491
Tested-by: Jenkins <ci@libreoffice.org>
Reviewed-by: Adolfo Jayme Barrientos <fitojb@ubuntu.com>
Diffstat (limited to 'README.md')
| -rw-r--r-- | README.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/README.md b/README.md index 1a91674665e7..1bbf9b58a481 100644 --- a/README.md +++ b/README.md @@ -16,8 +16,8 @@ A quick overview of the LibreOffice code structure. You can develop for LibreOffice in one of two ways, one recommended and one much less so. First the somewhat less recommended way: it is possible to use the SDK to develop an extension, -for which you can read the API docs [here](http://api.libreoffice.org/) -and [here](http://wiki.services.openoffice.org/wiki/Documentation/DevGuide). +for which you can read the API docs [here](https://api.libreoffice.org/) +and [here](https://wiki.openoffice.org/wiki/Documentation/DevGuide). This re-uses the (extremely generic) UNO APIs that are also used by macro scripting in StarBasic. @@ -68,7 +68,7 @@ Each module should have a `README` file inside it which has some degree of documentation for that module; patches are most welcome to improve those. We have those turned into a web page here: -http://docs.libreoffice.org/ +https://docs.libreoffice.org/ However, there are two hundred modules, many of them of only peripheral interest for a specialist audience. So - where is the |