Commit 35ea99f4 authored by Pekka Pessi's avatar Pekka Pessi

README, README.developers, docs/*: spell checked.

darcs-hash:20061207085938-65a35-01dcf5e723c5029315ff8995bbbcfbbe8af652ca.gz
parent c4c7d48d
......@@ -5,7 +5,7 @@ README / Sofia-SIP - RFC3261 compliant SIP User-Agent library
Introduction
------------
Sofia-SIP is an open-source SIP User-Agent library, compliant
Sofia-SIP is an open-source SIP User-Agent library, compliant
with the IETF RFC3261 specification. It can be used as
a building block for SIP client software for uses such as VoIP,
IM, and many other real-time and person-to-person communication
......@@ -40,7 +40,7 @@ the "sofia-sip/utils" directory:
- sip-options, query using SIP OPTIONS method
- sip-date, SIP date printer/parser
The Sofia-SIP su submodule also provides some small utils:
The Sofia-SIP su submodule also provides some small utilities:
- addrinfo (libsofia-sip-ua/su), resolve host names
- localinfo (libsofia-sip-ua/su), prints information about
......@@ -64,4 +64,4 @@ Licensing
---------
Sofia-SIP is licensed under terms of the GNU LGPL.
See the file "COPYING" for more infromation.
See the file "COPYING" for more information.
===============================================================
README.developers - Sofia-SIP development practises
README.developers - Sofia-SIP development practices
===============================================================
Introduction
......@@ -71,7 +71,7 @@ variables (see the library 'Makefile.am' files and
All changes to the library versions should be marked to the
appropriate library 'ChangeLog' file. The library version should
be changed at the same time as the first interface change is
commmitted since the previous release. The interface version is
committed since the previous release. The interface version is
frozen (should be marked to the 'ChangeLog' file) at the time
the next release is tagged (in other words, intra-release changes
need not be tracked with libtool versions).
......
=====================================================
Notes on compiling Sofia-SIP in different enviroments
=====================================================
======================================================
Notes on compiling Sofia-SIP in different environments
======================================================
Using GNU Autotools
-------------------
......@@ -38,3 +38,5 @@ Visual-C on win32
-----------------
See sofia-sip/win32/README.txt
LocalWords: automake
......@@ -62,7 +62,7 @@ Making the release tarball
- take a fresh checkout of the release using the release tag
sh> darcs get http://sofia-sip.org/repos/sofia-sip --tag=rel-sofia-sip-1_yy_z
- create the release tarball with "make distcheck"
- calculate md5 and sha1 hashes using md5sum and sha1sum utils,
- calculate md5 and sha1 hashes using md5sum and sha1sum utilities,
and copy the values to the release-notes (see below)
Creating the release notes and updating the website
......@@ -112,7 +112,7 @@ After release
Syncing CVS and darcs (or some other VCS)
=========================================
Some tips for synching from/to different version controlled
Some tips for synchronizing from/to different version controlled
tree.
- As CVS cannot trace file addition/move/removals, you need
......@@ -132,5 +132,5 @@ Checking API/ABI compatibility
- Use a unit test binary built against an old library,
to verify a new library version (forwards-compatibility).
- Use the 'icheck' tool (in Debian) to make comparsion
with two released versions.
- Use the 'icheck' tool (in Debian) to make comparison
between two released versions.
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment